Posts Tagged Windows
WSUS client error 0×80244022
Posted by Terje Skulstad in Software, Windows on August 17th, 2009
Ever seen this error “Error 0×80244022 occurred while downloading update notifying dependent calls” in your Windows Update.log?
Typically you have a Windows client, set up to use WSUS, but still you see that it keeps banging at http://update.microsoft.com for updates. Most likely this is caused by a corrupt download, and the best way (if you ask me) is to delete the WSUS client cache and let it check for updates on the local WSUS server instead.
To delete the cache:
On the client, stop the service “Automatic Updates”, delete (or rename) the SoftwareDistribution folder under %windir% (typically C:\Windows or C:\Winnt) and start the “Automatic Updates” service again.
Move the local WSUS update folder
Posted by Terje Skulstad in Software, Windows on July 14th, 2009
To move the WSUS content folder to a new location, use the wsusutil.exe. It’s located in C:\Program Files\Update Services\Tools\
To move the folder to d:\wsus you first have to create the folder, then run the wsusutil from the command line. Log file has to be specified.
wsusutil.exe movecontent d:\wsus d:\wsus.log
Depending on the size of the local update folder and disk speed, the content will eventually be moved to the new location.
As you can see from these before and after screenshots from the Share and Storage management snap-in in 2008, the util takes care of changing the shares.
Before:
After:
I noticed that the utility doesn’t seem to move the updates, but copy them. After the operation was complete, I had to delete the folder C:\WSUS manually (6GB).
More info on storing WSUS updates: http://technet.microsoft.com/en-us/library/bb245839.aspx
Windows 2008 Sysprep – join domain issue
Posted by Terje Skulstad in Software, Windows on June 23rd, 2009
This week I’ve made a template for Windows 2008 Standard x86 for deployment of new VM’s to our ESX Servers. Sysprep is now done through an XML-file instead of the usual INF file.
To use it, you first have to install the Windows Automated Installation Kit and use the Windows System Image Manager. It’s more advanced than the good old sysprep.
What I wanted was a base install which could be created from the VMWare template, given a name an joined to a domain. Then you can change the IP-adress afterwards.
After creating a new VM, installed VMWare Tools and ran sysprep, I tested the startup. The VM booted, asked for language and computer name. Punched in a new computer name and got the logon prompt.
When I tried logging in as the domain administrator I got an error “the security database on the server does not have a computer account for this workstation trust relationship”
After looking through the event log (security) I saw that there was a failure audit for Winlogon, and when I looked at the name logged it was different than the one I gave the machine during the mini-setup.
I found that the name I gave the machine was applied after the computer actually was joined to the domain, so it got an auto-generated name in Active Directory
Since I then tried to log on from a computer with a name changed only locally through OOBE there was a security mismatch.
I ran sysprep again and this time I checked what the machine name was in AD (you can find it in the Computers special container) and gave the same in the Welcome Wizard and voila! Success!
I’ve tried to find out why this happens, but it seems it’s meant to be this way. No way in the current version of WAIK to give the computer a name before it’s added to the domain, so I’m stuck with adding it to a workgroup and change the name/ join domain afterwards. Sorry Microsoft, but this is a step back…
According to some posts on the web, this is by design and you should use something like netdom or a script to change the computername and join the domain, but why the f… did they add the option to the Answer file?!?!?
How-to uninstall Internet Explorer 8
Posted by Terje Skulstad in Software, Windows on May 13th, 2009
I you want to uninstall IE8 and it won’t uninstall through add/remove program. Should apply to beta and release candidate (that was where I needed it). Program didn’t show up in add/ remove, but could be uninstalled through %systemroot%\ie8\spuninst\spuninst.exe.
I had to use this procedure since I first installed the beta. When I tried to install the final version, I wasn’t able to upgrade.
IO Error in application
Posted by Terje Skulstad in Software on April 21st, 2009
Had a case today with an application giving an IO error on a terminal server (Windows 2003 combined domain controller/ terminal server/ Citrix) . If logging in with a domain admin it worked just fine, but if a regular user tried to start it, it caused an IO error. After playing around with the security policy, I discovered it could be solved by giving the create global objects permission to the user.
Setting is under Default Domain Controller Policy –> Local Policies –> User Rights Assignment: Create global objects
Hiding the Cancel button in Windows XP Service Pack 3 install (or No Cancel, Back and Finish)»
Posted by Terje Skulstad in Software, Windows on April 6th, 2009
Yesterday I made my first AutoIT script. Excellent tool for tweaking with installs (and other windows) to make them more suitable for your needs. Go to http://www.autoitscript.com/ for the tool. Best of all, it’s free 
To make the button go away create a new AutoIT script and use the code below. Note: This script was developed for the Norwegian version of SP3 and translated to English. Since I haven’t tested the script on that version, I cannot guarantee that the Windows titles and button caption are 100% correct .
Code:
;Hides the AutoIT icon
Opt(“TrayIconHide”,1)
; 1st section gives the user a warning that the sevice pack install will start
$PID=SplashTextOn(“INFO from IT”, “Service Pack 3 install starting. Install time approximately 20 – 30 minutes and the machine will reboot automatically after the install”, 250, 200, -1, -1, 4, “10″)
Sleep(10000)
SplashOff()
ProcessWaitClose($PID)
; 2nd section is the actual run of the SP3. Runs in passive mode which basically auto accept the license agreement and sets the uninstall folder to default. I also set the /forcerestart to ensure that install is complete. This is of course optional.
Run ( “P:SPXP_SP3_NORi386updateupdate.exe /passive /forcerestart” )
; Wait for the SP3 window to be active
WinWaitActive( “Software Update Installation Wizard”, “” )
; Set the SP3 window active if it doesn’t have focus.
If Not WinActive(“Software Update Installation Wizard”,”") Then WinActivate(“Software Update Installation Wizard”,”")
; Hides the Cancel button
ControlHide ( “Software Update Installation Wizard”, “”, 2 )
; Hides the back button (not really necessary because it’s greyed out, but gives a cleaner look)
ControlHide ( “Software Update Installation Wizard”, “”, 12323 )
; Finish button, same reason as Back button
ControlHide ( “Software Update Installation Wizard”, “”, 12325 )
Figure 1: Standard SP3 install window with buttons
Figure 2: Running with buttons removed
All finished!!!
This is a repost of a previously published article due to transition to WordPress