This morning I had a very interesting query from a user. The request was if he could auto-download all the attachments that he received on his Outlook to another folder other than the temporary one (default folder). I sat down for a while looking for rules or any option on Outlook itself. But nothing to be found. When I did a bit of my own research, I figured out that with a bit of coding and then using the Outlook Rules itself, this was possible.
The link found to be very helpful for this purpose. Please note that in the section where one can specify the file type that needs to be stored to the custom folder, one needs to add a double quote before the file type.
For example, here is the code that I had used for my trial runs
Public Sub saveAttachtoDisk(itm As Outlook.MailItem)
In the scenario above, the user only wanted PDF files to be saved to a folder in his D drive. The part of the code where I have highlighted as red should have the file extension (file type) within double quotes. In the link provided above this has been given within single quotes.
Although it is mentioned that this works for Outlook 2007 and Outlook 2010, I had tried on Outlook 2013 and it works beautifully without any hiccups. Give it a try! It’s awesome to see it working!
If you are getting this error from your Server Event Logs; it is certain that your backup is not secure and urgent action needs to be taken
The high-probability for this error is that you are running on Older CDP Agent Version (possibly 6.0). With CDP Agent Version 6.0 there is an issue of agent resources leaking due to which the agent service has these panic attacks and restarts the service. In order to fix this issue it is advised to update your CDP Agent to latest available version; which as of currently is 22.214.171.124
Very recently, I happened to go through a very tricky situation with the printers in our office, all connected through SafeQ ports (not IP ports). The users would print, but when they went to the printers to release the jobs, the jobs were not displayed on the YSoft Terminal. I checked the print server queue and couldn’t find any pending jobs stuck in the queue. I tried restarting both the Print spooler services, that didn’t help. I tried restarting both the CML (Primary Server) and the Secondary Node (Secondary Server) and this helped for about 5 minutes. After 5 minutes or so the prints would stop appearing on the YSoft SafeQ terminal.
After having checked for more than 2 hours, I realized that the secondary partition on the Secondary server had run out of space. When checked, I was shocked to find that the ldf file for the SafeQ Database has consumed almost 90% of space on the secondary partition. Once this file was truncated, the jobs had started appearing on the terminals and the print jobs were all smooth, fast and back to normal.
After installing Movie Maker, you face the below error as illustrated
You may go through the link that shows up in the error and check the minimum system requirements. The only pointer that may catch your attention is the DirectX Version on your PC. The minimum DirectX Version expected is version 9.
To crosscheck this click Start – Type Dxdiag and press enter. The DirectX Version will be listed in the DirectX Diagnostic Tool Window that opens up. If your PC is relatively new and frequently updated; there is no reason why your DirectX Version should be below 10; so forget the minimum requirement of DirectX 9 for Movie Maker 2012
The most obvious solution to get your Movie Maker software working is to update your Display Driver
Locate your Display Driver Model and Driver Version