Startup script is not doing its job
I have set a startup script with GPO on Computer Configuration to uninstall an application from computers, but it seems that the script is not running since it doesn't remove it at all. When Executing the script manually it does its job perfectly.Below is the script content:@echo off msiexec.exe /q /m MSIOYVNO /x "\\DCname\SHarename\ScrewDrivers Client v410498.msi" C:\PROGRA~1\triCerat\SIMPLI~1\SCREWD~1\UNWISE.EXE /s C:\PROGRA~1\triCerat\SIMPLI~1\SCREWD~1\INSTALL.LOG msiexec.exe /q /m MSIUJKCO /x "\\DCname\SHarename\ScrewDrivers Client v4.1.07.27.msi" msiexec.exe /q /m MSIOYVNO /x "\\DCname\SHarename\ScrewDrivers Client v4.2.01.44.msi" msiexec.exe /q ALLUSERS=2 /m MSIBPJVO /i "\\DCname\SHarename\ScrewDrivers Client v4.4.0.1 (rdp only).msi" /norestartclose
June 23rd, 2009 11:40am

Hi,Please note that startup scripts run under the local SYSTEM account's context which, by default, has no network access (hence, it is unable to access the share from which the msi packages are located). When you invoke the script manually, it runs under the current logged in user's context which may have the requisite permissions on the share. A workaround is to assign permission to the "Domain Computers" group to the share. When the LSA tries to connect to network resources, it is seen as COMPUTERNAME$ (where, COMPUTERNAME is the NetBios name of the client). This is to overcome the network access limitation for the LSA.Alternatively, if the applications are published via a GPO, the user can just go to the Add/Remove control panel applet to uninstall the applications.Regards,Salvador Manaois IIIMCITP | Enterprise & Server AdministratorMCSE MCSA MCTS(x5) CIWA C|EH My Blog: Bytes and BadzMy Shots:View MyPhotoStream
Free Windows Admin Tool Kit Click here and download it now
June 23rd, 2009 12:28pm

it doesn't work even with task scheduler via GPO.I have configured this task to execute with domain admin account, but it doesn't do it's job completely
June 23rd, 2009 12:49pm

Hi, Thank you for your post. To better understand the issue, please help collect the following information: 1. What operating system is running on the computers? 2. How did you install the application? SMS? Group Policy? Or Manually installed? 3. Does the policy successfully apply to the computers? Please run the Group Policy Results wizard (in GPMC) to verify it. 4. Is there any event/error logged? You can add the "/l" option to the script to generate Windows Installer log. Command-Line Optionshttp://msdn.microsoft.com/en-us/library/aa367988(VS.85).aspx I look forward to your response.
Free Windows Admin Tool Kit Click here and download it now
June 24th, 2009 9:50am

thank you for reply,1. WinXP w/SP32. Manually, GPO, SCCM (as you can see on script commands, I am trying to uninstall all versions of the same application)3. gpresult shows that the Policy has been applied succesfully, and some parts of the script are executed. I will bold format the lines that are applied successfully on computers and italic format the ones that are not applied succesfully msiexec.exe /q /m MSIOYVNO /x "\\DCname\SHarename\ScrewDrivers Client v410498.msi" C:\PROGRA~1\triCerat\SIMPLI~1\SCREWD~1\UNWISE.EXE /s C:\PROGRA~1\triCerat\SIMPLI~1\SCREWD~1\INSTALL.LOG msiexec.exe /q /m MSIUJKCO /x "\\DCname\SHarename\ScrewDrivers Client v4.1.07.27.msi" msiexec.exe /q /m MSIOYVNO /x "\\DCname\SHarename\ScrewDrivers Client v4.2.01.44.msi" msiexec.exe /q ALLUSERS=2 /m MSIBPJVO /i "\\DCname\SHarename\ScrewDrivers Client v4.4.0.1 (rdp only).msi" /norestart4. There are 4 events written after the GPO is applied- Event ID: 1704 Source: SceCli Description: Security policy in the Group policy objects has been applied successfully.- Event ID: 1807 Source: SecurityCenterDescription: The Security Center service has been stopped. It was prevented from running by a software group policy.- Event ID:308 Source: Application ManagementDescription: Changes to software installation settings were applied successfully.
June 24th, 2009 4:09pm

Hi, Thank you for your response. For startup script, the possible causes could be: 1. The computer account does not have enough permission to read and execute .msi file. 2. While the startup script is executed, the network may not be ready. Suggestions: 1. Check share folder permission --------------------------------------------- a. Right click on the shared folder that stores the .msi files, under Sharing tab, click on Permissions, make sure Everyone has Full Control. b. On the Security tab, make sure "Authenticated Users" group has at least Read & Execute permission. Authenticated Users group contains computer accounts. 2. Disable Fast Logon feature ----------------------------------------- a. Edit a GPO that applies to the computer, navigate to: Computer Configuration/ Policies / Administrative Templates / System /Logon b. Enable the policy "Always wait for the network at computer startup and logon". For additional information about fast logon, please refer to the following article: Description of the Windows XP Professional Fast Logon Optimization feature http://support.microsoft.com/kb/305293 If the issue persists, please collect the following information on a Windows XP computer for further research: 1. Userenv debug logging: a. Please enable userenv debug logging on a Windows XP computer: How to enable user environment debug logging in retail builds of Windows http://support.microsoft.com/kb/221833 b. Restart the computer to reproduce the issue. 2. MPSReport: a. Download MPSReport from the following linkhttp://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd915706/MPSRPT_DirSvc.EXEb. Double-click the executable to launch the report gathering tool on the client workstation.c. After the tool finishes gathering the information, you will a .cab file in C:\WINDOWS\MPSReports\DirSvc\cab folder. 3. Please zip the files above and upload to the following space: https://sftasia.one.microsoft.com/choosetransfer.aspx?key=36cf5aa0-6d15-48e6-b94f-ff3ac062614d Password: _0!kN$dpO36Kwuot For the scheduled tasks preference policy, please ensure that the Group Policy preference client-side extensions have been installed on the Windows XP computer. Information about new Group Policy preferences in Windows Server 2008 http://support.microsoft.com/kb/943729 Meanwhile, please view the SchedLgU.Txt log on the Windows XP computer to check if the task completed successfully. How to troubleshoot scheduled tasks in Windows XP and in Windows Server 2003 http://support.microsoft.com/kb/308558 I look forward to your response.
Free Windows Admin Tool Kit Click here and download it now
June 26th, 2009 5:43am

Hi, Just want to check the current status of the issue. Please feel free to let me know if I can assist further. Have a nice day.
July 1st, 2009 5:06am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics