Archive for January, 2009
WSUS 3.1 and the SelfUpdate Virtual Directory
Sunday, January 18th, 2009 | Tech Help | 5 Comments
I came back from my extended leave to find that my workstations and servers had not checked into the WSUS server for months. After a bit of detective work the issue came down to the SelfUpdate virtual directory in IIS was missing. The Microsoft help page details how to fix the issue but wasn’t completely helpful. More on that later.
Here is what I did to get my clients checking in again.
Check the folder permissions on the SelfUpdate directory, located at C:\Program Files\Update Service\SelfUpdate. Make sure the permissions like this;
| Group | Permissions |
| Administrators | Full Control |
| System | Full Control |
| Domain/Users or Local/Users | Read&Execute, Read, List Folders |
| IUSR_ComputerName | Read&Execute, Read, List Folders |
In my case the IUSR_ComputerName permission was missing.
After adding the correct permissions I looked for the re-installation msi, Selfupdate.msi. The only problem is that the SelfUpdate re-installation msi was not found on my WSUS server. Turns out in the recent WSUS update to 3.1 this installer can become corrupted and not installed on the server.
To get the Virtual Directory back I would have to install it by hand. Here are the settings you need to create it;
Open Internet Information Services (IIS) Manager. Right click on the “Default Web Site” and choose;
- New
- Virtual Directory…
- It started the VD Creation Wizard
- Alias = SelfUpdate
- Path = C:\Program Files\Update Services\SelfUpdate
- Finish the wizard.
- Right click on the newly SelfUpdate and choose Permissions.
- I added “Authenticated Users” and gave them the default rights:
- Read & Execute
- List Folder Contents
- Read
After completing these steps I ran “wuauclt /detectnow” on each of my servers. I left the workstations to check in on their own.
Within 12 hours the number of missing clients had gone from nearly 200 to less than 50. Once everyone logs in on Monday morning this number should dwindle to nothing.
Diskeepers Business Practices
Tuesday, January 13th, 2009 | Tech News | 2 Comments
I have been using Diskeeper’s products for 6 years and have commented on them before. It is my opinion that their products are slipping.
But another review of their products is not the reason for this post. I received a Christmas card from them this year and inside of it was a quote from L. Ron Hubbard, of Scientology fame. I thought it was quite odd to feature a quote from him inside a Xmas card and noted it on Twitter, saying something along the lines of “seriously thinking of ending my business with Diskeeper”.
Not long after a had a comment on said Tweet which informed me of a legal dispute with a former employee suing Diskeeper for forcing Scientology down his throat.
I really cannot stand the integration of church/religion and state or your place of employment. I do not care that it was a quote from the writer of this classic pile of crap or if it had been a quote from the Pope, or the Dalai Lama. Leave your preaching to your personal life.
So this ends my business relationship with Diskeeper. Time to find a new application to keep my disks unfragmented. Note: On home machines I like Defraggler
Better Late Than Never
Saturday, January 10th, 2009 | Tech News | Comments Off
The Windows 7 Beta launch yesterday had its share of problems and the Windows 7 team took notice. They have extended the beta download time and increased the number of keys beyond the 2.5 million initially slated for download.
I tried for most of Friday to get my keys but was unable to get past the green circle of death. Today the process was painless and carefree.
I haven’t had the time to install it yet, but look forward to doing so and seeing if the hype meets expectations.
Printers = Hate
Monday, January 5th, 2009 | Tech Help | Comments Off
A user reported an issue with her printer this afternoon. Whenever she tried to print it locked up her PC. I tried all my usual tricks to hack out the offending job, but nothing I tried was working. The print spooler would crash seconds after starting. This error kept taunting me:
“Spoolsv.exe – Application Error”
“The instruction at “0×77fcc2c0″ referenced memory at “0×00000000″.
“The memory could not be written.”
I popped out my trusty Troubleshooting Swiss Army Knife (read: Google) and quickly had another tool to fight the tenacious spooler.
It turns out the most common cause of the error is an abundance of .SHD and .SPL files in the spool directory. These files are created by the spooler to save the spooled data of a print job. The .SPL file comprises drawing commands and the .SHD file comprises job settings information of the print job.
To fix spoolsv.exe application error, you will have to remove these files from the system. To do this, perform the following steps on your Windows XP computer:
- Open Control Panel, select Performance and Maintenance, select Administrative Tools and then select the Services option.
- In the Services management console, locate the Spooler services, right-click on it and select Stop.
- Next, open the C:\Windows\System32\Spool\Printers folder. (Here, we are assuming that your Windows is installed in the default C:\Windows folder)
- Delete all the .SHD and SPL files from this folder.
- Next, open the TMP folder and delete all old and unused files from this folder.
- Finally, restart the Spooler service from the Services management console.
Just like that the users printer problems disappeared.
Search
Popular Posts
Photos
Popular Tags
Get Spiceworks!
