clivebuckwheat

Well at least now I have no compile errors anymore but now the installers do not run, but it picks up the OS type architecture type and then nothing. The installers reside on a map drive Z:\VerdiemSurveyor\Clientx86\Verdiem Surveyor Client.msi Z:\VerdiemSurveyor\Clientx64\Verdiem Surveyor Client.msi Any thoughts as to why the script is not executing the msi's. It is picking up the correct os type and the correct cpu/architecture? '''''''''''''''''''' '''''''''''''''''' ' ' Variable Declaration ' ''''''''''''''''''''' ''''''''''''''''' Dim myOS, myArch, myServiceName, myServiceDisplayName, myRunningState, myStatus, myExec Dim strComputer, oWMIService, colOSInfo, oOSProperty, strOSFamily strComputer = "." ''''''''''''''''''''' ''''''''''''''''' ' ' OS Name ' ''''''''''''''''''''' ''''''''''''''''' Set oWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2") Set colOSInfo = oWMIService.ExecQuery("Select * from Win32_OperatingSystem") For Each oOSProperty in colOSInfo strCaption = oOSProperty.Caption Next myOS = strCaption ''''''''''''''''''''' ''''''''''''''''' ' ' Architechture Type - 32 vs 64 bit ' ''''''''''''''''''''' ''''''''''''''''' Set WshShell = CreateObject("WScript.Shell") OsType = WshShell.RegRead("HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\PROCESSOR_ARCHITECTURE") If OsType = "x86" then myArch = 32 elseif OsType = "AMD64" then myArch = 64 end if '''''''''''' ' SERVICES ' '''''''''''' Const wbemFlagReturnImmediately = &h10 Const wbemFlagForwardOnly = &h20 arrComputers = Array("localhost") For Each strComputer In arrComputers Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\CIMV2") Set colItems = objWMIService.ExecQuery("SELECT * FROM Win32_Service", "WQL", wbemFlagReturnImmediately + wbemFlagForwardOnly) For Each objItem In colItems If objItem.DisplayName = "Verdiem Surveyor Client" Then myServiceName = objItem.Name myServiceDisplayName = objItem.DisplayName myRunningState = objItem.State myStatus = objItem.Status If myRunningState <> "Running" Then Return = objItem.StartService() If Return = 0 Then WScript.Echo "Service started" Else WScript.Echo "Service could not be started. Return = " & Return myRunningState = "Not Running" End If End if End if Next Next ''''''''''''''''''''' ''''''''''''''''' ' ' Debug print ' ''''''''''''''''''''' ''''''''''''''''' WScript.Echo "OS: " & myOS WScript.Echo "Arch: " & myArch WScript.Echo "Service Name: " & myServiceName WScript.Echo "Service Display Name: " & myServiceDisplayName WScript.Echo "Running State: " & myRunningState WScript.Echo "Status: " & myStatus ''''''''''''''''''''' ''''''''''''''''' ' ' Install Logic ' ''''''''''''''''''''' ''''''''''''''''' Dim oShell Set oShell = WScript.CreateObject ("WScript.Shell") If myServiceDisplayName <> "Verdiem Surveyor Client" Then If myRunningState <> "Running" Then If myOS = "XP" Then Wscript.Echo "Execing Client32 on XP" oShell.run "msiexec.exe /i ""Z:\VerdiemSurveyor\Clientx86\Verdiem Surveyor Client.msi"" /qb SERVER_NAME=myservername.ca SERVER_PORT=5600" End if If myOS = "Microsoft Windows 7 Professional" Then If myArch = 32 Then WScript.Echo "Executing Client32 on 7" oShell.run "msiexec.exe /i ""Z:\VerdiemSurveyor\Clientx86\Verdiem Surveyor Client.msi"" /qb SERVER_NAME=myservername.ca SERVER_PORT=5600" End if if myArch = 64 Then WScript.Echo "Executing Client64 on 7" oShell.run "msiexec.exe /i ""Z:\VerdiemSurveyor\Clientx64\Verdiem Surveyor Client.msi"" /qb SERVER_NAME=myservername.ca SERVER_PORT=5600" End if End if Else WScript.Echo "Install condidtions not met... Aborting" End if End if Set oShell = Nothing

Hi I have to push out a software called verdiem that controls power management to over 1000 pc's based on the os. If it is xp 32 bit /windows 7 32 bit then install the 32 bit client, if it is windows 7 64 bit then install the 64 bit client. if the service already is present to nothing, I been able to piece meal together scripts I found from the internet to detect the os, and the service, but I can't get the program to run from a shared drive using osshell.run command. I'd really appreciate some help this is really urgent and I have been stuck for 3 days. '''''''''''''''''''''''''''''''''''''' ' ' Variable Declaration ' '''''''''''''''''''''''''''''''''''''' Dim myOS, myArch, myServiceName, myServiceDisplayName, myRunningState, myStatus, myExec Dim strComputer, oWMIService, colOSInfo, oOSProperty, strOSFamily strComputer = "." '''''''''''''''''''''''''''''''''''''' ' ' OS Name ' '''''''''''''''''''''''''''''''''''''' Set oWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2") Set colOSInfo = oWMIService.ExecQuery("Select * from Win32_OperatingSystem") For Each oOSProperty in colOSInfo strCaption = oOSProperty.Caption Next myOS = strCaption '''''''''''''''''''''''''''''''''''''' ' ' Architechture Type - 32 vs 64 bit ' '''''''''''''''''''''''''''''''''''''' Set WshShell = CreateObject("WScript.Shell") OsType = WshShell.RegRead("HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\PROCESSOR_ARCHITECTURE") If OsType = "x86" then myArch = 32 elseif OsType = "AMD64" then myArch = 64 end if '''''''''''' ' SERVICES ' '''''''''''' Const wbemFlagReturnImmediately = &h10 Const wbemFlagForwardOnly = &h20 arrComputers = Array("localhost") For Each strComputer In arrComputers Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\CIMV2") Set colItems = objWMIService.ExecQuery("SELECT * FROM Win32_Service", "WQL", wbemFlagReturnImmediately + wbemFlagForwardOnly) For Each objItem In colItems If objItem.DisplayName = "Verdiem Surveyor Client" Then myServiceName = objItem.Name myServiceDisplayName = objItem.DisplayName myRunningState = objItem.State myStatus = objItem.Status If myRunningState <> "Running" Then Return = objItem.StartService() If Return = 0 Then WScript.Echo "Service started" Else WScript.Echo "Service could not be started. Return = " & Return myRunningState = "Not Running" End If End if End if Next Next '''''''''''''''''''''''''''''''''''''' ' ' Debug print ' '''''''''''''''''''''''''''''''''''''' WScript.Echo "OS: " & myOS WScript.Echo "Arch: " & myArch WScript.Echo "Service Name: " & myServiceName WScript.Echo "Service Display Name: " & myServiceDisplayName WScript.Echo "Running State: " & myRunningState WScript.Echo "Status: " & myStatus '''''''''''''''''''''''''''''''''''''' ' ' Install Logic ' '''''''''''''''''''''''''''''''''''''' Dim oShell Set oShell = WScript.CreateObject ("WScript.Shell") If myServiceDisplayName <> "Verdiem Surveyor Client" Then If myRunningState <> "Running" Then If myOS = "XP" Then Wscript.Echo "Execing Client32 on XP" oShell.run "msiexec.exe /i" "Z:\VerdiemSurveyor\Clientx86\Verdiem Surveyor Client.msi /qb SERVER_NAME=myservername.ca SERVER_PORT=5600" End if If myOS = "Microsoft Windows 7 Professional" Then If myArch = 32 Then WScript.Echo "Execing Client32 on 7" oShell.run "msiexec.exe /i" "Z:\VerdiemSurveyor\Clientx86\Verdiem Surveyor Client.msi /qb SERVER_NAME=myservername.ca SERVER_PORT=5600" End if if myArch = 64 Then WScript.Echo "Execing Client64 on 7" oShell.run "msiexec.exe /i" "Z:\VerdiemSurveyor\Clientx64\Verdiem Surveyor Client.msi /qb SERVER_NAME=myservername.ca SERVER_PORT=5600" End if End if Else WScript.Echo "Install condidtions not met... Aborting" End if End if Set oShell = Nothing

To bad I was hoping to learn how to add critical boot drivers via the sysprep.xml. Nevertheless I thank you for your response and time,

Thanks man you peak my interest. Let me know.

so this VM file how do you deal with boot-crtical devices?, if you can't inject them using dsim into the vm file?. To inject files it has to be a wim file ?

so the people that still use ghost, have to image the machine with the wim file and then make the ghost file?, is this correct?. As for as I know you cannot image down a wim file using ghost only imagex, correct?

So let me get this straight, you make a master in Vmware, make the wim, inject all the drivers you need via dsim into the wim then imaged it back down to the virtual and make your ghost image?

I guess I have to test on real hardware. Something I was hoping to avoid to the later stages. Before I test 1. I have put all the drivers in C:\DRIVERS 2. I have pointed the devicepath in the registry to C:\Drivers is that all I have to do before I seal with sysprep. should I mention the drivers folder in the sysprep.xml file as well, or is it not needed.

Hi I have to install some software that I need to know what OS is installed before hand. If it is Winxp or win7 32 then run this installer if it is Win 7 64 bit run another installer, Also I have to check if it already installed, it runs as a service, so I have to check and see if the services exists and if it does do nothing else check the os version and install the appropriate installer how can I do this via batch?

thank you worked like a champ

does anyone know how to add boot critical drivers via the sysprep.xml file?. I believe this is what I have to do.

I put the vmware scsi driver in My c:\drivers folder and it is still blue screening. I don't even think it is accessing the c:\drivers folder ant all can someone take a look at my Panther logs folder. I have not learned how to read these yet and more importantly understand them. panther.zip

If you are using ghost, you *must* ghost from the real hardware. The cannot install the device driver for a boot device, it *must* be already installed in the image. Cheers Derek The driver is in the c:\drivers folder but I believe that noo drivers at all are being installed from the C:\Drivers during the sysprep process.

It seems that no drivers are being installed from the C:\Drivers I have changed HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DevicePath in the registry to point to C:\Drivers. Is there anything I have to do in my sysprep.xml file to make this happen as well?

What would be the fastest way to push this to a lab?, no other elements will be needed except the dreamweaver component. I thought I'd ask the experts on this forums. As they always help me get it done the right way.

Thank you Cluberti, I did some additional research and you confirmed things for me. A KMS volume activation server is the way to go for the college.

So I can;t test my universal image on a viertual to work out the bugs, it has to be on a physical hardware. Do you think there reason why it is blue screening is because I am testing on a vmware machine.

Another question. Would any of these mak tools help our activation woes at our school? Any advice would help. http://www.microsoft.com/downloads/en/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en http://technet.microsoft.com/en-us/library/ff793438.aspx http://www.microsoft.com/downloads/en/details.aspx?FamilyID=311e7e71-ea1d-4ddd-bb36-b68349dd9539&displaylang=en

Thank you all for the replies. This board makes me better than I am. I will have more knowledge when I call Microsoft now. Thanks.

Thank you Cluberti, as always you have help me so much, It is hard to say how much we re-image due to the fact we work in a school and we have class additions at the spur of the moment with software requests. Can you tell me if Office 2010 has KMS key as well?. I am looking for the best possible solution for the college.

I am in charge of 6 Windows 7 labs, we have a MAK serial number for Windows 7 and Office 2010 from Microsoft. After imaging we have scripted the activations of Office 2010 and Windows 7 which works perfect. It does the activation over the internet. It's part of our post imaging configurations. Here is where we run into problems. Everytime we re-image a lab, and activate Windows 7 and Office 2010 using the same post configuration method as described above, we use an additional license. So our count at Microsoft is all screwed up. Is there anything thing I should be doing on my master pc BEFORE deploying it to my labs, like releasing the license first before making the image etc etc. I wanted to ask here before I call Microsoft. Is there anything specific I should ask Microsoft when I call them. As far as I can see from our license agreement we have a MAK serial number for both Windows 7 and Office 2010. Any help /advice would be a great asset before I call Microsoft to investigate this

A standalone exe would be great that doesn't have to be installed. I would like to get a list of all applications and the version numbers, which I can export to a text file, word file or excel spreadsheet. Can someone recommend such a utility?

Not using wim file, we use ghost. I put all my drivers in C:\Drivers (from bashrats) pointed the devicepath to c:\drivers in the registry. I did my initial test on a vmware virtual, and it BSOD-ED I will try it on actual hardware next. The drive type on the virtual says scsi I believe.

I get a stop 000000000x7b error. How can I debug this one?.

after sysprep but before the reboot yes. so have it open? HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\DevicePath this is the current key right?