Wednesday, July 27, 2011

Windows Autologon script

Here is a script you can use to set a Windows PC to autologon. Edit the script and set the variables to your desired settings.

Monday, July 25, 2011

VPMSECE.DLL errors in Outlook

These errors usually occur when something has changed, like the Symantec Endpoint Server address or a Symantec reinstall. You may be able to fix this error by deleting the extend.dat file from Outlook.

Close Outlook.

On XP browse to: C:\Documents and Settings\%username%\Local Settings\Application Data\Microsoft\Outlook. Delete the extend.dat file.

Reopen Outlook and see if error goes away.

On Windows 7 or Vista browse to: C:\Users\%username%\AppData\Local\Microsoft\Outlook. Delete the extend.dat.

Reopen Outlook and see if error goes away.

Friday, July 01, 2011

Windows 7 Printer Driver Installation Error 0x00000057

*Update - we are seeing this issue less these days.  Are many of you still having this issue?  If so, please describe for me in the comments section so I can see if I can recreate the pattern or if I can come up with a better solution.  Or email me.

We are seeing this error when attempting to install printers (drivers) on new Windows 7 builds. The simplest solution I have found is reboot the computer and log on with a different administrative account. Often then the printer driver can be installed without getting the error.

Here's another thing I have found. Running procmon during the installation shows 'access denied' on C:\Windows\System32\DriverStore\infpub.dat. Try editing the security on this file and add the local Administrators to it, will full control. After doing this I've had success getting printer drivers to install that would give the error 0x00000057. Note - it may be necessary to change the security on all of the .dat files in the DriverStore folder to get the driver to install. Here's a script that will change the security on all the files for you.

*****Note***** - This problem is not limited to printer drivers.  Also, if you use my script, as ridiculous as it sounds, you have to be quick.  Get everything ready to perform the driver install, run the script, and then run the install, as quickly as possible after running the script.  You are racing against windows resetting the permissions.

Also, I have noticed after changing the permissions on the files Windows will change them back, removing what you have added.

If you need help on changing the permissions on the file maybe these will help:

Change permissions on C:\Windows\System32\DriverStore\infpub.dat to include Administrators with Full Control.

Browse to C:\Windows\System32\DriverStore
Right click the file infpub.dat
Choose Properties
Click Security Tab
Click Edit Button
Click Add Button
Click Locations button and choose the local computer account (should be first item in list)
In the box type: Administrators
Click Check Names – this should come back underlined
Click Ok
With Administrators highlighted, put a checkmark in the checkbox next to Full Control
Click Ok
Click Ok
Retry installing the printer driver.

New beginner's guide to PowerShell on my GitHub page

 I created a beginner's guide to PowerShell here: https://github.com/aamjohns/Powershell_Guide/blob/main/README.md I hope it helps someo...