Jamie's Blog

The password stored in Credential Manager is invalid.

Problem:

When a user was printing documents it would show up under a help desk person’s account.

Also was seeing a bunch of EventID 552 like these in the security logs

Logon attempt using explicit credentials:
Logged on user:
User Name: USER1
Domain: DOMAIN
Logon ID: (xxx,0x7D052)
Logon GUID: {xxxxxxx-07b5-8f5f-d5dd-d78268681b37}
User whose credentials were used:
User Name: HELPDESKUSER
Domain: DOMAIN.LOCAL

Logon GUID: –
For more information, see Help and Support Center at

Solution:

After enabling NetLogon debug logging information. http://support.microsoft.com/kb/109626

This would appear in the System Log under Kerberos Warning:

The password stored in Credential Manager is invalid. This might be caused by the user changing the password from this computer or a different computer. To resolve this error, open Credential Manager in Control Panel, and reenter the password for the credential XXX.

I was able to launch the Credential Manager using “rundll32.exe keymgr.dll,KRShowKeyMgr” and delete the cached credentials for the server that was running under the help desk person’s account.

Rebooted the PC and the user’s print jobs now show up under the correct account.

Extended Mimosa NearPoint attachment not opening

Problem:
After double clicking on email with extended attachment the email comes right up without loading Mimosa. No attachment is available.

Resolution:
1. Corrupt Form Cache -> Clear Cache -> Restart Outlook
2. If that does not work, make sure allow forms that bypass Outlook is checked

CopyProfile does not process and causes Windows could not parse or process the Unattend answer file for the pass [Specialize]

The following error appears if CopyProfile setting is set to true configured in the unattend.xml file.

Windows could not parse or process the Unattend answer file for the pass [Specialize]. The settings in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows-Shell-Setup]

Solutions was to delete any users from the following location in the registry that do not exist anymore
HKLM\Software\Microsoft\Windows NT\CurrentVersion\ProfileList

After doing that you should be able to sysprep the gold image correctly.

Windows 7 Sysprep could not initialize. There are one or more Windows updates that require a reboot.

The following error continued to appear when trying to run sysprep

I rebooted several times and the error would not go away. I resolved the issue by using “Program And Features” to install solitaire,  rebooting, and then removing solitaire using “program and feature” option.

After following those steps I was able to get around the issue, I think it was due to something getting hung up along the way and adding a new program reset the correct flags.

Microsoft Office Outlook Cannot Provide Form Scripting Support On Terminal Server

Microsoft Office Outlook cannot provide form scripting support

• If this is occuring on a Terminal Server it is by default as Micrsoft does not allow VBS to run on TS.

A workaround can be applied by:

* Copy the Program Files\Microsoft Office\OfficeXXXX\Outlvbs.dll file from a computer that is not 
       running Microsoft Outlook onto the Terminal Server.
* Delete all registry entries for OutlookVBScript on the TS
* Exit Outlook and go back in.

PC Reboots When Connecting With Remote Desktop

The reason for pc’s restarting when attempting to open a Remote Desktop session is due to an outdated video driver, specifically Intel. The correct video driver is noted below. This is for the 82945G chipset. The update driver version that works is version 6.14.10.4926.  

http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=16835&lang=eng