Error installing Office 2010 RTM
The final version of Office 2010 was released to Technet and MSDN subscribers yesterday. When I tried to upgrade my primary Windows 7 virtual machine on my Mac I got the following error complaining that I had the beta version installed:
Path variables in batch files
This is another post documenting something I used to fix a problem at work so I don’t forget about it. We were pushing out Firefox to all our systems yesterday via SCCM. It’s pushed out using a batch file to configure various things, and I noticed that although the batch file was being called from the dozen or so distribution points we have, the script was calling back to the main server. I’ve seen this before but never looked into a solution. I started searching for a variable or a way to get the path the script is run from and found this article posted in 2008 on myITforum.com. It is addressing the exact situation I was encountering.
Failure when injecting Windows 7 drivers into a SCCM 2007 OSD boot image
This problem was driving me nuts for the last week, and is more for my own memory than anything else. At work we got a demo unit from HP of the desktop computer we’re going to be rolling out this summer and I was updating the network drivers in our OS Deployment boot images. The Windows PE environment wasn’t getting the network drivers installed and finally I saw the error message “The selected driver is not applicable to any supported platforms.”
The fix was easy. Microsoft KB 978754 has a hotfix that needs to be installed on the SCCM Site Server, then the server needs to be rebooted. The drivers then installed without a problem. The KB article says the cause of the issue was the driver importing wizard couldn’t recognize drivers signed for only Windows 7.
Good to know.
PowerShell: Add printers to DNS
I realized today that most of our printers at work did not have DNS entries. This isn’t a big problem for users because they’re on our print server and they get their printers through Group Policy. The Print server has each printer set up to the IPs. We just implemented a management system today, and it lists the printers by IP and because the DNS entries were “Unknown” for most of them, it wasn’t easy to determine what printer we were looking at.
I found several PowerShell examples on the web for interacting with Microsoft DNS servers, and took a bit from each to come up with this script. It takes the shared printer name and publishes that as the DNS name. This does cause a problem if you have spaces in a share name, but our environment doesn’t, so I didn’t program for that issue.
Here’s the script:
Apple Predictions
With all the Apple tablet rumors preceding the upcoming Apple event at the end of the month, I thought I’d put down my thoughts about what’s going to be announced. They’re listed in order of most-likely to pipe-dreams.