zorg2000k

Hi, Looking for some advise on this if possible. Current set up as follows. Windows XP SP2 / SP3 running bginfo via registry : [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run] "BGINFO"="Bginfo.exe c:\\windows\\system32\\gds1.bgi /timer:0" This has no wallpaper enabled, plain blue background colour set. What I'm looking to do is over the December period have a different wallpaper image applied every day. We have GPO and Quest installed for applying GPO's. Any help would be great. Thanks in advance.

Hi, Been trawling through the forums but can't seem to find anything on what I'm trying to achieve. I have a OSD created WIM file of a XP machine. What I was hoping to do was mount that wim file and integrate any missing XP hotfixes. I can find lots of details about doing this with msu Vista files but nothing on XP .exe files. Has anyone got any help on this. Cheers

Hi, Been trawling through the forums but can't seem to find anything on what I'm trying to achieve. I have a OSD created WIM file of a XP machine. What I was hoping to do was mount that wim file and integrate any missing XP hotfixes. I can find lots of details about doing this with msu Vista files but nothing on XP .exe files. Has anyone got any help on this. Cheers

Hi, Fixed my issue with this code, may help someone. %SYSTEMDRIVE%\packagedapps\PDU_APP\wpi.hta sleep 60 goto processcheck :mshtaRunning sleep 60 :processcheck TASKLIST | %windir%\SYSTEM32\find.exe /I "mshta.exe " && goto mshtaRunning exit

Hi, Been using WPI for sometime. Great tool. Moved onto the latest version but I am having some issues launching the hta.exe. My machine joins the domain then runs a batch file to run some printer / programs default settings, as part of the bat file I call the hta.exe like this : start /w %windir%\system32\mshta.exe c:\packagedapps\PDU_APP\wpi.hta Now this would normally stop the original batch file until I choose my programs to install from WPI. Once WPI finishes the installs it would then finish the batch file and reboot. I can see a white page launch then dissapear, then the batch file continues, as it start to shutdown the white page appears again and then I see my WPI splash screen, but this goes as the machine is shutting down. I did enter a sleep command after the start /w %windir%\system32\mshta.exe c:\packagedapps\PDU_APP\wpi.hta which works but is not something I would like to do. Any help would be great. My config file is for WPI Config 7.2.0+ Cheers

Since this is a registry tweak, I suggest u try monitor thru Regshot Unicode A quick check reveal my test m/c (XP) registry key is at HKLM\SYSTEM\ControlSet001\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}\0003\HcDisableSelectiveSuspend: 0x00000001 HKLM\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}\0003\HcDisableSelectiveSuspend: 0x00000001 Uncheck "Allow the computer to turn off this device to save power." will create these 2 keys on my own test m/c. I'm unsure it is standard or m/c dependant. Thanks for the reply. Not used that reg tool before, very handy. Been trying with regmon but to much info in logs. Just need to test on a few other machines but they all look the same other than some going from 0000 to 0007. Cheers

Hi, My work has now moved vendor for its hardware. The problem I have is that now we have two types of hardware my OSD image requires updating. Everything works fine (SATA working , thanks to article from this forum ) other that an issue with the USB Root Hub - Power Management Settings. What I was hoping for is a reg setting to disbale the "USB Root Hub - Power Management Settings - allow the computer to turn off this device to save power" option. i.e uncheck this box accross multiple hardware machines. I would then be able to apply this as reg fix as a post install through OSD , so it shouldn't matter on the make of machine / hardware type. Thanks in advance Stuart

Hi, I hope i'm posting in the correct forum Looking for some help on an issue I have n capturing an image in OSD 2003. The set up I have is a VMware ESX virtual image with Windows XP SP2 with the relevant SCSI LSI drivers added into the base OS image. The build has completed fine and I know want to sysprep this VM image into our live SMS 2003 server. When I run the sysprep it all loks great and eventually turns the machine off. I then power up the image and boot from CD. It then scan the image and starts to capture the image up to my server. Now every time it reaches 1058mb in the capture it turns the VM ware XP workstation off, so it fails to capture the whole image. At first I thought it may be a corrupt file when it could see the last folder it was using before it closed down. So I deleted that folder and tested again. This time it went further but still failed when it reached 1058mb in the capture phase. Beginning to pull my hair out now, what I have left anyway !!! Any help would be great Cheers

Hi, My work has now moved vendor for its hardware. The problem I have is that now we have two types of hardware my OSD image requires updating. Everything works fine other that an issue with the USB Root Hub - Power Management Settings. What I was hoping for is a reg setting to disbale the "USB Root Hub - Power Management Settings - allow the computer to turn off this device to save power" option. i.e uncheck this box. I would then be able to apply this as reg fix as a post install through OSD , so it shouldn't matter on the make of machine / hardware type. Thanks in advance Zorg

Hi, Does anyone have a reg tweak to set all images files to open in Windows Picture and Fax Viewer for all profiles i.e admin, all users and localadm ??? This is a manual process we do at the moment here as part of our reference machine before using sysprep. thanks in advance Zorg

Works a treat thanks

Thanks for the reply, What I am looking for is a script that will search through all *.txt files in c:\ for a txt value within the .txt file and replace it with another text value. Something like this. Within the follow 1-3.txt files I want to search and replace say "DAMREM004202" to "DAMREM004203" 1.txt DAMREM004202 FOUSAF0000022 CRDCRR000010P1 2.txt DAMREM004202 POLLH00005502 CRDCRR000010P1 3.txt DAMREM004202 DRTCA0000022 CRDCRR000010P1 Hpe this helps. Zorg

Hi, Not sure if this is the best section in this forum for help. Here's hoping Looking for some help in scripting a batch file to do the following. I have a dir full of folders that contain lots of txt files. The naming conversion for the txt files are all different. The txt file contents look like this : DAMREM004202 FOUSAF0000022 CRDCRR000010P1 What I want the batch file to do is look for say "DAMREM004202" and update all the txt files that contain that reference to say "DAMREM004203" This is an application stack that we use with OSD to deploy applications. Problem we have found is when it comes to update the software to a new version we will have to update all txt files so the new software version is used if we need to rebuild the machine from OSD. Thanks for you help in advance Zorg

Hi, Could you explain the above script as it is not working correctly. Cheers Zorg

Our base OSD build get's updated every three months with all MS patches. We are implementing ITMU within the next three months but need to continue patching our existing estate of 15000 machines. Own dir for each patch just to make it easier to maintain. This is a copy of a standard XP.bat file. Echo off %windir%\system32\reg.exe QUERY "HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB923694" /v Description | %windir%\system32\find.exe "923694" && goto out %windir%\system32\reg.exe QUERY "HKLM\SOFTWARE\Microsoft\Updates\Outlook Express 6\SP1\KB923694-OE6SP1-20061106.120000" /v Description | %windir%\system32\find.exe "923694" && goto out %windir%\system32\reg.exe QUERY "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CSDVersion | %windir%\system32\find.exe "Service Pack 2" && goto xpsp2patch :xppatch KB923694_OE6.0sp1.exe /QUIET /NORESTART goto end :xpsp2patch KB923694_SP2.exe /QUIET /NORESTART :end %windir%\system32\reg.exe add HKLM\Software\GDS\VersionControl\PatchControl /v Reboot_Pending /t REG_SZ /d 1 /f :out %windir%\system32\xcopy.exe /Y KB923694.exe c:\smsinstall goto finish :NotReq %windir%\system32\xcopy.exe /Y KB923694NA.exe c:\smsinstall :finish These files are added for reporting purpose as our SMS server only reports on .EXE's. due to bandwith issues. %windir%\system32\xcopy.exe /Y KB923694.exe c:\smsinstall %windir%\system32\xcopy.exe /Y KB923694NA.exe c:\smsinstall

Thanks for this. Looks good will need to test now.

Hi, Finally got my work batch file for patching up and running covering XPSp1 / XPSp2 / 3 version's of Office / Visio / Project. Have a question though. My script is now a meaty 14 pages long . Is it possible to reduce my script in someway with regards to the following : My Xp patches call the following cd MS06-011 call XP.bat cd.. cd MS06-014 call XP.bat cd.. cd MS06-015 call XP.bat cd.. cd MS06-018 call XP.bat cd.. cd MS06-022 call XP.bat cd.. etc. All the way down to Ms07. Any thoughts ? Cheers in advance. Zorg

Just a thought but what is preventing you from using ITMU now? The hardest part of your solution is creating the detection logic and that alone is valuable time that SMS could be fixing your computers. Within one detection cycle after advertising the sync agent you would have a complete picture of what you need to fix and the packages you need to create. Even better, the reports for software compliance are updated along with the inventory so you can track your progress much mroe easily, something your homegrown solution will probably not do. OS detection is easy but ITMU gives you the rest of the detection. If your waiting for SMS 2003 SP3, that will be out on 27 APR 07 (ie Friday) and its more than worth it to switch and take two weeks to figure it out rather then reinvent the wheel. If your network is as borked as you say it is (been there, done that way too much), spending the week or so to figure out how to use ITMU which is not that hard will more than payoff in total time to completion. SGT Gruhn, John L BCT1 D101 S6 AMO NCOIC Thanks again for the reply. We have a very complex change management / strategic agenda process in place, which have set the timescales for this change. Might just have to live with what is there at present and fix if possible. Cheers Stuart

Hi, thanks for the reply Mason and JohnGruhn. We will be moving to IMTU within the next 6 months or so but I need to resolve this now as it is now begining to cause issue's where machines are not being patched. I managed to have this mess dumped on me as it was being rotated around a team of tech's that never used the standards scripts that were provided to them to use I have had another thought today about a different method. Any thoughts on this or help ? What I would do is create a master list of KB files for SP1 / SP2 /WIN2K. Query for machine type. Then query the reg against that list of KB file for that machine type. Pipe out the list of missing KB files then install those KB files. Sounds easy but any help would be great. Cheers Stuart

Hi. thanks for the reply. I should of said that that is not an option here at present. Needs to be done by SMS.

If there are any SMS / Batch guru's out there that have a better way in deploying patches via sms then any feedback / help would be great. Even better are there any tools /apps that may help in in my quest Is this the best forum for this type of query ??? Cheers Stuart

Hi, Hope this is the correct forum. I have a large network of around 10,500 computer's that we run an SMS job ,weekend's , nightly and sometime's daily, for updating to the latest MS patches. The script below is the main batch file that is called. I will try to breakdown each area. :start If Exist %windir%\System32\reg.exe goto WksCheck copy /Y \\ngsysm02\smssource\Desktop\SMSUtils\reg.exe %windir%\system32\ :WksCheck rem check to see if system is a workstation %windir%\system32\reg.exe query "HKLM\SYSTEM\CurrentControlSet\Control\ProductOptions" /v ProductType | %windir%\system32\find.exe /i "WinNT" && goto WkStation goto Main_exit :WkStation rem Utility Check and Copy routines :Filever rem Check for FileVer.exe If Exist %windir%\System32\filever.exe goto FileVer-VerChk copy /Y \\ngsysm02\smssource\Desktop\SMSUtils\filever.exe %windir%\system32\ :FileVer-VerChk %windir%\system32\filever.exe /A /D %windir%\System32\filever.exe | %windir%\system32\find.exe "5.2.3790.0" && goto qchaincpy copy /Y \\ngsysm02\smssource\Desktop\SMSUtils\filever.exe %windir%\system32\ :qchaincpy rem check for qchain.exe If Exist %windir%\System32\qchain.exe goto qchain-VerChk copy /Y \\ngsysm02\smssource\Desktop\SMSUtils\qchain.exe %windir%\system32\ :qchain-VerChk %windir%\system32\filever.exe /A /D %windir%\System32\qchain.exe | %windir%\system32\find.exe "5.0.2195.6666" && goto sleepcpy copy /Y \\ngsysm02\smssource\Desktop\SMSUtils\qchain.exe %windir%\system32\ :sleepcpy rem check for sleep.exe If Exist %windir%\System32\sleep.exe goto sleep-VerChk copy /Y \\ngsysm02\smssource\Desktop\SMSUtils\sleep.exe %windir%\system32\ :sleep-VerChk %windir%\system32\filever.exe /A /D %windir%\System32\sleep.exe | %windir%\system32\find.exe "5.0.2134.1" && goto psshutdowncpy copy /Y \\ngsysm02\smssource\Desktop\SMSUtils\sleep.exe %windir%\system32\ :psshutdowncpy rem check for psshutdown.exe If Exist %windir%\System32\psshutdown.exe goto psshutdown-VerChk copy /Y \\ngsysm02\smssource\Desktop\SMSUtils\psshutdown.exe %windir%\system32\ :psshutdown-VerChk %windir%\system32\filever.exe /A /D %windir%\System32\psshutdown.exe | %windir%\system32\find.exe "2.32.0.0" && goto addregval copy /Y \\ngsysm02\smssource\Desktop\SMSUtils\psshutdown.exe %windir%\system32\ :addregval rem add reboot key and value to registry %windir%\system32\reg.exe add HKLM\Software\GDS\VersionControl\PatchControl /v Reboot_Pending /t REG_SZ /d 0 /f rem If XP, launch xp.bat %windir%\system32\reg.exe query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentVersion | %windir%\system32\find.exe "5.1" && goto XP_Launch rem If W2K, launch 2K.bat %windir%\system32\reg.exe query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentVersion | %windir%\system32\find.exe "5.0" && goto 2K_Launch rem If NT4, launch nt4.bat %windir%\system32\reg.exe query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentVersion | %windir%\system32\find.exe "4.0" && goto NT_Launch goto office_launch :XP_Launch call XP_Patches.bat goto office_Launch goto shutdowncheck :2K_Launch call 2K_Patches.bat goto office_Launch :NT_Launch call NT_Patches.bat goto office_Launch :office_Launch :Word2k3_check if exist "C:\Program Files\Microsoft Office\OFFICE11\WINWORD.EXE" goto Excel2k3_Check goto WordXP_check :Excel2k3_Check if exist "C:\Program Files\Microsoft Office\OFFICE11\EXCEL.EXE" goto Powerpoint2K3_Check goto WordXP_check :Powerpoint2K3_Check if exist "C:\Program Files\Microsoft Office\OFFICE11\POWERPNT.EXE" goto Office2k3_Install goto WordXP_check :WordXP_check if exist "C:\Program Files\Microsoft Office\OFFICE10\WINWORD.EXE" goto ExcelXP_Check goto Word2Kcheck :ExcelXP_Check if exist "C:\Program Files\Microsoft Office\OFFICE10\EXCEL.EXE" goto PowerpointXP_Check goto Word2Kcheck :PowerpointXP_Check if exist "C:\Program Files\Microsoft Office\OFFICE10\POWERPNT.EXE" goto OfficeXP_Install goto Word2Kcheck :Word2Kcheck if exist "C:\Program Files\Microsoft Office\OFFICE\WINWORD.EXE" goto Excel2K_Check goto shutdowncheck :Excel2K_Check if exist "C:\Program Files\Microsoft Office\OFFICE\EXCEL.EXE" goto Powerpoint2K_Check goto shutdowncheck :Powerpoint2K_Check if exist "C:\Program Files\Microsoft Office\OFFICE\POWERPNT.EXE" goto Office2K_Install goto shutdowncheck :Office2k3_Install call Office2K3_Patches.bat goto shutdowncheck :OfficeXP_Install call OfficeXP_Patches.bat goto shutdowncheck :Office2K_Install call Office2K_Patches.bat goto shutdowncheck :shutdowncheck %windir%\system32\reg.exe QUERY "HKLM\Software\GDS\VersionControl\PatchControl" /v Reboot_Pending | find "1" && goto psshutdown goto Main_exit :psshutdown %windir%\system32\qchain.exe c:\smsinstall\qchain.txt %windir%\system32\psshutdown.exe -f -r -t 28800 -m "All Required MS Security patches have been installed and a reboot is required - to stop this automated reboot countdown please manually reboot this computer at any suitable safe time prior to the 8hr deadline." %windir%\system32\reg.exe add HKLM\Software\GDS\Reboot /v Reboot_Pending /t REG_SZ /d 0 /f goto flagchecks :flagchecks :MS03 %windir%\system32\reg.exe query "HKLM\Software\GDS\VersionControl\PatchControl\OSPatch" /v MS03_Complete | %windir%\system32\find.exe "1" && goto MS04 goto dirty_exit :MS04 %windir%\system32\reg.exe query "HKLM\Software\GDS\VersionControl\PatchControl\OSPatch" /v MS04_Complete | %windir%\system32\find.exe "1" && goto MS05 goto dirty_exit :MS05 %windir%\system32\reg.exe QUERY "HKLM\Software\GDS\VersionControl\PatchControl\OSPatch" /v MS05_Complete | %windir%\system32\find.exe "1" && goto MS06 goto dirty_exit :MS06 %windir%\system32\reg.exe QUERY HKLM\Software\GDS\VersionControl\PatchControl\OSPatch /v MS06_Complete | %windir%\system32\find.exe "1" && goto MS07 goto dirty_exit :MS07 %windir%\system32\reg.exe QUERY HKLM\Software\GDS\VersionControl\PatchControl\OSPatch /v MS07_Complete | %windir%\system32\find.exe "Feb2" && goto Main_exit goto dirty_exit :Main_exit exit /b 0 :dirty_exit exit /b 10 1. The first part of the above script copies a few tools to the %windir%\system32 folder for future use. 2. The second part adds a reg value for quering (found later) 3. We have a few type's of machines on the network at the moment . Most are XPsp2 but we have a few NT4 and Win2K machines. So a query is run to find out what type of machine it is then it run's the relevant batch file. i.e xp_patches.bat 2k_patches.bat nt4_patches.bat I will concentrate on the xp_patches.bat as the 2k_patches.bat and nt4_patches.bat run in the same manner. Below is the batch file of my xp_patches :MS03 %windir%\system32\reg.exe query "HKLM\Software\GDS\VersionControl\PatchControl\OSPatch" /v MS03_Complete | %windir%\system32\find.exe "1" && goto MS04 cd MS03-037 call MS03-037Install.bat cd.. %windir%\system32\reg.exe add HKLM\Software\GDS\VersionControl\PatchControl\OSPatch /v MS03_Complete /t REG_SZ /d 1 /f :MS04 %windir%\system32\reg.exe query "HKLM\Software\GDS\VersionControl\PatchControl\OSPatch" /v MS04_Complete | %windir%\system32\find.exe "1" && goto MS05 cd MS04-028 call MS04-028Install.bat cd.. cd MS04-030 call MS04-030-XP.bat cd.. cd MS04-031 call MS04-031-XP.bat cd.. cd MS04-034 call MS04-034-XP.bat cd.. cd MS04-037 call MS04-037-XP.bat cd.. cd MS04-040 call XP.bat cd.. cd MS04-041 call XP.bat cd.. cd MS04-043 call XP.bat cd.. cd MS04-044 call XP.bat cd.. %windir%\system32\reg.exe add HKLM\Software\GDS\VersionControl\PatchControl\OSPatch /v MS04_Complete /t REG_SZ /d 1 /f :MS05 %windir%\system32\reg.exe QUERY "HKLM\Software\GDS\VersionControl\PatchControl\OSPatch" /v MS05_Complete | %windir%\system32\find.exe "1" && goto MS06 cd MS05-007 call XP.bat cd.. cd MS05-013 call XP.bat cd.. cd MS05-017 call XP.bat cd.. cd MS05-018 call XP.bat cd.. cd MS05-026 call XP.bat cd.. cd MS05-027 call XP.bat cd.. cd MS05-033 call XP.bat cd.. cd MS05-036 call XP.bat cd.. cd MS05-040 call XP.bat cd.. cd MS05-041 call XP.bat cd.. cd MS05-042 call XP.bat cd.. cd MS05-043 call XP.bat cd.. cd MS05-044 call XP.bat cd.. cd MS05-045 call XP.bat cd.. cd MS05-047 call XP.bat cd.. cd MS05-048 call XP.bat cd.. cd MS05-049 call XP.bat cd.. cd MS05-050 call XP.bat cd.. cd MS05-051 call XP.bat cd.. cd MS05-053 call XP.bat cd.. cd MS05-054 call XP.bat cd.. %windir%\system32\reg.exe add HKLM\Software\GDS\VersionControl\PatchControl\OSPatch /v MS05_Complete /t REG_SZ /d 1 /f :MS06 %windir%\system32\reg.exe QUERY HKLM\Software\GDS\VersionControl\PatchControl\OSPatch /v MS06_Complete | %windir%\system32\find.exe "1" && goto MS07 cd MS06-001 call XP.bat cd.. cd MS06-002 call XP.bat cd.. cd MS06-006 call XP.bat cd.. cd MS06-007 call XP.bat cd.. cd MS06-008 call XP.bat cd.. cd MS06-011 call XP.bat cd.. cd MS06-015 call XP.bat cd.. cd MS06-018 call XP.bat cd.. cd MS06-022 call XP.bat cd.. cd MS06-023 call XP.bat cd.. cd MS06-024 call XP.bat cd.. cd MS06-025 call XP.bat cd.. cd MS06-030 call XP.bat cd.. cd MS06-032 call XP.bat cd.. cd MS06-033 call XP.bat cd.. cd MS06-034 call XP.bat cd.. cd MS06-036 call XP.bat cd.. cd MS06-041 call XP.bat cd.. cd MS06-045_Fix call MS06-045_Fix.bat cd.. cd MS06-050 call XP.bat cd.. cd MS06-051 call XP.bat cd.. cd MS06-052 call XP.bat cd.. cd MS06-053 call XP.bat cd.. cd MS06-056 call XP.bat cd.. cd MS06-057 call XP.bat cd.. cd MS06-060 call WordView.bat cd.. cd MS06-063 call XP.bat cd.. cd MS06-064 call XP.bat cd.. cd MS06-065 call XP.bat cd.. cd MS06-066 call XP.bat cd.. cd MS06-067 call XP.bat cd.. cd MS06-068 call XP.bat cd.. cd MS06-069 call XP.bat cd.. cd MS06-070 call XP.bat cd.. cd MS06-071 call XP.bat cd.. cd MS06-073 call XP.bat cd.. cd MS06-074 call XP.bat cd.. cd MS06-075 call XP.bat cd.. cd MS06-076 call XP.bat cd.. cd MS06-078 call XP.bat cd.. rem the data value (after /d) must be changed to correspond to the naming convention described above %windir%\system32\reg.exe add HKLM\Software\GDS\VersionControl\PatchControl\OSPatch /v MS06_Complete /t REG_SZ /d 1 /f :MS07 %windir%\system32\reg.exe QUERY HKLM\Software\GDS\VersionControl\PatchControl\OSPatch /v MS07_Complete | %windir%\system32\find.exe "Feb2" && goto leave cd MS07-004 call XP.bat cd.. cd MS07-005 call XP.bat cd.. cd MS07-006 call XP.bat cd.. cd MS07-007 call XP.bat cd.. cd MS07-008 call XP.bat cd.. cd MS07-009 call XP.bat cd.. cd MS07-011 call XP.bat cd.. cd MS07-012 call XP.bat cd.. cd MS07-013 call XP.bat cd.. cd MS07-016 call XP.bat cd.. rem Microsoft Critical Patch 05/04/2007 cd MS07-017 call XP.bat cd.. rem Microsoft Critical Patch 11/04/2007 cd MS07-019 call XP.bat cd.. rem Microsoft Critical Patch 11/04/2007 cd MS07-020 call XP.bat cd.. rem Microsoft Critical Patch 11/04/2007 cd MS07-021 call XP.bat cd.. rem Microsoft Important Patch 11/04/2007 cd MS07-022 call XP.bat cd.. %windir%\system32\reg.exe add HKLM\Software\GDS\VersionControl\PatchControl\OSPatch /v MS07_Complete /t REG_SZ /d Apr1 /f :leave The script will look in the patchcontrol area in the reg for value called MS03_complete, MS04_complete, MS05_complete etc If this value is found then that means that the machine has been completely patched for that MS range i.e MS05. If the value is not found then it will continue on installing each of the MS patches until it reaches the end of the above script. Below is the xp.bat file that is called for each on the MS patches, although the patche's , data may change they all follow the same method. :MSPatchCheck rem reg query to identify if the patch is installed. %windir%\system32\reg.exe QUERY "HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB926436" /v Description | %windir%\system32\find.exe "926436" && goto out rem reg query to see if XP-SP2 is installed. %windir%\system32\reg.exe QUERY "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CSDVersion | %windir%\system32\find.exe "Service Pack 2" && goto xpsp2 :xpsp1 rem XP sp1 patch files here WindowsXP-KB926436-x86-custom-ENU.exe /QUIET /NORESTART goto end :xpsp2 rem XP sp2 patch files here WindowsXP-KB926436-x86-ENU.exe /QUIET /NORESTART goto end :end rem Sets time of PC net time /set /y rem add reboot flag to registry %windir%\system32\reg.exe add HKLM\Software\GDS\VersionControl\PatchControl /v Reboot_Pending /t REG_SZ /d 1 /f :out rem Copies Flag file to smsinstall folder. md c:\smsinstall copy /Y KB926436.exe c:\smsinstall\KB926436.exe goto finish :NotReq rem Copies Flag file to smsinstall folder. md c:\smsinstall copy /Y KB926436NA.exe c:\smsinstall\KB926436NA.exe :finish 1. It first check's the reg to see if it has been patched already. If already patched it goes to out and creates a dummy file "KB926436.exe" within a folder called c:\smsinstall then exit's. This is done for SMS reporting as we one sweep for .exe in SMS 2003. Thsi is to help with a slow network infrastructure. 2. If the reg value is not found it queries for XPsp1 or XPsp2 and then install's the relevant MS patch and then copies the dummy file to c:\smsinstall then exit's and move's onto the next patch foler as in MS07-12 etc. My question is. I have been tasked in making this process as simple as possible. If anyone has any idea's or comments on the above, please leave me a reply. Cheers Stuart

Hi, I have a few cmd's with msi and mst commands within that require to be run from the local disc. I can copy the content off my WPI disc but in WPI 5.6 what command would I use to call the CMD file from the temp folder ? Thanks in advance Zorg

Hi, Thanks for the reply. This is what I started with, but the issue is when this attempts to logon i.e. reboot then ctrl/Alt/del our work XP build has a splashscreen. If you press ok it then logs on using the username and password entered in reg. Any thoughts Cheers Stuart

Hi, Looking for some help. I have an app to install that requires a reboot and then a log back on to complete the install. What I need to try and get round is our XP in the office has a splashscreen when you press ctrl/Alt/del before you get to enter username / password. What I need the script to do is : 1. Install first part of app and reboot. (this is working and also applies a reg for part 4) 2. Get to ctrl/Alt/del screen and press an ok button. 3. Enter admin username and password (Fails because of part 2) 4. Complete second part install. (once logged on it installs) Thanks in advance Stuart