| J.C. 的个人资料J.C.'s space日志网络 |  工具  帮助 |
|
|
3月11日 Windows Update Error -- WindowsUpdate_80240019Ok, I just had an issue with WSUS. None of my servers were updating and I was getting a WindowsUpdate_8024001 whenever I tried to update a Vista/Server 2008 server. And the windowsUpdate.log file was showing the following errors:
2009-03-11 21:28:55:852 608 1170 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190194
2009-03-11 21:28:55:852 608 1170 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190194 2009-03-11 21:28:55:852 608 1170 Misc WARNING: DownloadFileInternal failed for http://computer.domain.net/selfupdate/wuident.cab: error 0x80190194 2009-03-11 21:28:55:852 608 1170 Setup WARNING: SelfUpdate check failed to download package information, error = 0x80244019 2009-03-11 21:28:55:852 608 1170 Setup FATAL: SelfUpdate check failed, err = 0x80244019 2009-03-11 21:28:55:852 608 1170 Agent * WARNING: Skipping scan, self-update check returned 0x80244019 2009-03-11 21:28:55:852 608 1170 Agent * WARNING: Exit code = 0x80244019 Not sure how it happened, but the root cause was a missing Virtual Directory on the WSUS default website. I added a Virtual Directory called SelfUpdate to the default website and pointed it to the C:\Program Files\Update Services\Selfupdate directory. I gave it full permissions, but I doubt it need all of those.
This solved my problem. Of course I checked the GPO to make sure that the update point was correct there. And I checked the Registry of computers to ensure that the had the update point listed correctly as well (meaning they were getting the GPO properly).
For those of you interested in the post mortem. I am not sure what caused the disappearance of the Selfupdate Virt Directory. I was standing up a Forefront Client Security Server with all roles and retiring my old WSUS server. Somewhere along the line it either was not created or was deleted. 12月18日 32-bit Print Drivers in a 64-bit WorldOk, I just had an adventure trying to upload drivers to a 64-bit 2008 printer server.... Here's how I finally made that happen. To install 32-bit drivers on a 64-bit Windows Server 2008 print server is a bit complicated (as I found out). To install the 32 bit drivers, you must do so from a 32-bit client.
1. From the 32-bit client you will add the printer. You will get a message about the driver not being available on the server and you will be given the chance to install one. 2. Install the appropriate 32-bit driver. Note: the 32-bit driver must match the name of the 64-bit (i.e. if the driver installed for the HP LJ 3220 printer on the Printer Server is an HP LJ3200 driver, then the 32-bit driver must also be the HP LJ3200 driver, even if there is a specific 32-bit HP LJ3220 driver. The server and client drivers must be the same!) 3. Open the printer properties on the client system. 4. Navigate to the sharing tab. 5. Add additional Drivers. 6. Select the appropriate environments and versions (XP, 2000, Windows 98). 7. Select OK and provide a location for the driver (if necessary). 8. Viola! The printer drivers will be installed on the server. |
|
|
