tobias-tobin

How about something like this: /uninstall [ProductID] Removes the specified product from the user's computer. Look up the value of [ProductID] in the Setup.xml file for the product you want to modify. Example \\server\share\Office12\setup.exe /uninstall Pro where Office12 is the root of the network installation point. You would need to determine the product ID for InfoPath. I would check out this thread. It has some good information in it: http://www.appdeploy.com/messageboards/tm.asp?m=61759&mpage=1&key=ﰶ After reading the above linked thread it looks like you might want to use the /modify command line option: /modify [ProductID] Used with a modified Config.xml file to run Setup in maintenance mode and make changes to an existing Office installation. For example, you can use the /modify option to add or remove features. Look up the value of [ProductID]in the Setup.xml file for the product you want to modify. Not sure on this just throwing out some information that might help. The final product could be a batch file with the command line in it that you then run with SCCM. BTW - I went ahead and tried this myself. I kept getting a window that the installation was corrupted. So I don't know if the above will work for you.

Hi, Could you integrate the autologon registry settings into your image and then remove them with a script when the computer joins the domain (using a GPO script)?

There's also AdminStudio. Again, you will have to pay for it: http://www.flexerasoftware.com/products/adminstudio.htm

Do you use SCCM or Group Policy in your environment? You should be able to do this with a script and execute it using SCCM or GPO.

Are you wanting to collect the information from all your systems and record it somewhere or are you just wanting to be able to look at a system and see what version it has? A software query using PSInfo will tell you the version of Configuration Manager Client installed. Example, PSInfo query of a remote XP SP3 system returns the software with this as one of the items: Configuration Manager Client 4.00.6487.2000 More information on what you are trying to do would help. You could also probably get this information straight from your SCCM server with a query. Probably not helpful but trying...

The Usmtsize.txt file contains a list of values—one for each cluster size. The first column of numbers is the cluster size and the second column is what the store size will be for that cluster size. The first line is the cluster used for the drive where usmtsize.txt was created. The estimate that you will want to use is the line with the cluster size matching the storage drive (for example, the cluster size of your file server). These estimates use some assumed values and may not always provide a high degree of accuracy in the estimation process. Next, here's a link telling you how to get your cluster size of the disk: http://support.microsoft.com/kb/245436 Get your cluster size and then look in the second column for how many bytes it is (the store estimate). I hope this helps.

Here's the query we use to isolate Windows 7 systems: select distinct SMS_R_System.Name, SMS_R_System.SMSAssignedSites, SMS_R_System.IPAddresses, SMS_R_System.IPSubnets, SMS_R_System.OperatingSystemNameandVersion, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.LastLogonUserDomain, SMS_R_System.LastLogonUserName, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceId, SMS_R_System.NetbiosName from SMS_R_System where SMS_R_System.OperatingSystemNameandVersion like "%Workstation 6.1%"

Hi Trevor, Thank you for your response. I agree except it is happening with different drivers (HP, Dell, Brother). And throw in the fact that it doesn't always happen makes it more mysterious to me. Yes we are. And as part of the MDT2010 deployment I have it updating the system as the pre-software install step. But I've also got the image fully patched. Double coverage I guess. We do the software installs later with SCCM. I appreciate your thoughts and suggestions. BTW - your site is awesome. Very well written and informative. I like it. AJ.

We've started rolling out Windows 7 x64 as our new build (replacing XP systems). Not long after getting started on the rollout we've been encountering this error when we go to install a printer driver. It is bizarre in that it does not happen to every system, but it does happen to a significant number of systems. I believe I have found a work around but it just doesn't seem right that this is happening and that we should have to use a workaround. My work around is changing the permissions on the .dat files located at C:\Windows\System32\DriverStore folder. By default these files have System with full control, and users with read. That's all. If we add administrators with full control, then we can install the printer driver without getting the error. But the sad thing is a process or service changes the permissions back on these files. I'm wondering if we are the only people seeing this? I've googled it and it is not unheard of. It sounds like the problem started with Vista. But why is this happening? Are any of you encountering this problem? Thanks, AJ.

According to Microsoft: So it sounds like you might want to disable the UAC. I work in an enterprise environment and we disable it. It can be the root of many headaches.

Great eye Lucid. I will double check my script. I hope that was the issue. Thanks!

On the ESX host try changing the NIC setting to auto-negotiate. According to this thread it fixed the problem for someone else: http://social.technet.microsoft.com/Forums/en/mdt/thread/dbc70c7e-f82d-464b-b5d0-bcdf2261f1fc

I'm trying to do a very basic operation - that is - delete a shortcut that we do not want on the desktop. The file is located at C:\Users\Desktop\Username\File.lnk. When I try to do this scriptomatically, I get access denied. What do I need to do to accomplish this by script? Thanks, Tobias.

Maybe the path needs to be in quotation marks? If there are spaces in the name or path maybe that is the issue? I don't know just throwing something out there

We have WSUS with SP2 installed and ALL of our Windows 7 Enterprise clients show up as Vista Enterprise. Has anyone else seen this and does anyone know of a fix for this? Thanks, Tobias.