HK10/100 Posted April 5, 2010 Share Posted April 5, 2010 Hi everyone, I've been trying to create a 32-bit 7 unattended with our Enterprise media and product key. My problem is that the MAK/Volume license product key doesn't go in the same place as a retail product key in the autounattend.xml and Windows setup rejects the key as "invalid". However, if I leave the key blank the unattended works fine. Once in windows I use "slmgr.vbs -ipk" and "slmgr.vbs -ato" to replace the default enterprise key and activate Windows. My problem is that the slmgr vbs generates a result dialogue "The product key xxxxx-xxxxx-xxxxx-xxxxx-xxxxx was successfully installed." and you have to press an OK button. I would like to do this the right way and have the key built into the autounattend.xml. I was wondering if anyone out there who was working with 7 Enterprise could post their autounattend so I could see where the key should go? or any other idea's/suggestions they may have. Thanks Link to comment Share on other sites More sharing options...
MrJinje Posted April 5, 2010 Share Posted April 5, 2010 Depending on the "title" of the pop up window, you just need create a asynchrononous vbs script that waits for that particular window to appear and it will close it. Something like this.Kill_Pop_Up.vbsSet WshShell = Wscript.CreateObject("WScript.Shell")Do While Not Wshshell.AppActivate ("What Ever Pop Up Title Is")Wscript.sleep 1000LoopWshshell.AppActivate "What Ever Pop Up Title Is"Wshshell.SendKeys "%{F4}"I would start the script either immediately before/after running your SLMGR commands. Link to comment Share on other sites More sharing options...
HK10/100 Posted April 5, 2010 Author Share Posted April 5, 2010 Depending on the "title" of the pop up window, you just need create a asynchrononous vbs script that waits for that particular window to appear and it will close it. Something like this.Kill_Pop_Up.vbsSet WshShell = Wscript.CreateObject("WScript.Shell")Do While Not Wshshell.AppActivate ("What Ever Pop Up Title Is")Wscript.sleep 1000LoopWshshell.AppActivate "What Ever Pop Up Title Is"Wshshell.SendKeys "%{F4}"I would start the script either immediately before/after running your SLMGR commands.That's another option. I'm trying to put the key into the autunattend file, but I may have to do it the way you suggested if I can't figure it out. ThanksKeep the suggestions coming. Link to comment Share on other sites More sharing options...
cluberti Posted April 5, 2010 Share Posted April 5, 2010 It would actually probably be more reliable outside the file - using slmgr as a task to run once the image is deployed. Link to comment Share on other sites More sharing options...
maxXPsoft Posted April 5, 2010 Share Posted April 5, 2010 (edited) or any other idea's/suggestions they may have. I found also you can't put in the xml so do this after setup or even during setupcomplete.cmdSTART /WAIT /B cscript //nologo %windir%\system32\slmgr.vbs -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx >nulEDIT: You can call that during oobesystem from a <FirstLogonCommands> cmds since you are using an xml Edited April 6, 2010 by maxXPsoft Link to comment Share on other sites More sharing options...
derniwi Posted April 6, 2010 Share Posted April 6, 2010 Which tool do you use for deploying?Using MDT 2010 it is possible to enter the KMS key into a task sequence.And if you are using MAK, the VAMT can send the MAK key to the client.Regards, Nils. Link to comment Share on other sites More sharing options...
HK10/100 Posted April 6, 2010 Author Share Posted April 6, 2010 (edited) Okay, so I solved my own problem by muddling through Microsoft's volume activation deployment guide. But I thought I would share in case anyone needed it in the future. Thanks to those who posted their suggestions. <?xml version="1.0" encoding="utf-8"?><unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="windowsPE"> <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SystemLocale>en-us</SystemLocale> <UserLocale>en-us</UserLocale> <UILanguage>en-US</UILanguage> <UILanguageFallback>en-us</UILanguageFallback> <InputLocale>0409:00000409</InputLocale> </component> <component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <UserData> <ProductKey> <Key></Key> <WillShowUI>OnError</WillShowUI> </ProductKey> <Organization>_</Organization> <FullName>_</FullName> <AcceptEula>true</AcceptEula> </UserData> <ImageInstall> <OSImage> <InstallFrom> <MetaData wcm:action="add"> <Key>/IMAGE/NAME</Key> <Value>Windows 7 ENTERPRISE</Value> </MetaData> </InstallFrom> </OSImage> </ImageInstall> </component> </settings> <settings pass="oobeSystem"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <UserAccounts> <LocalAccounts> <LocalAccount wcm:action="add"> <Name>Owner</Name> <Group>Administrators</Group> <Password> <PlainText>true</PlainText> <Value></Value> </Password> </LocalAccount> </LocalAccounts> </UserAccounts> <OOBE> <HideEULAPage>true</HideEULAPage> <NetworkLocation>Work</NetworkLocation><ProtectYourPC>2</ProtectYourPC> <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE> </OOBE> </component> <component name="Microsoft-Windows-International-Core" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <UILanguage>en-US</UILanguage> <UserLocale>en-US</UserLocale> <InputLocale>0409:00000409</InputLocale> </component> </settings> <settings pass="specialize"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <ProductKey>XXXXX-XXXXX-XXXXX-XXXXX-XXXXX</ProductKey> <<<---MAK PRODUCT KEY GOES HERE! <AutoLogon> <Enabled>true</Enabled> <Username>Owner</Username> <Password> <Value /> </Password> <LogonCount>9999999</LogonCount> </AutoLogon> <TimeZone>Eastern Standard Time</TimeZone> <ComputerName>Rev4-1-10</ComputerName> </component> </settings> <cpi:offlineImage cpi:source="wim:C:/Users/Someguy/Desktop/Windows_7_Unattended/GRMCENVOL_EN_DVD/sources/install.wim#Windows 7 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" /></unattend>Now to figure out how to trigger program installations... Edited April 6, 2010 by HK10/100 Link to comment Share on other sites More sharing options...
maxXPsoft Posted April 7, 2010 Share Posted April 7, 2010 (edited) Okay, so I solved my own problem by muddling through Microsoft's volume activation deployment guide.<<<---MAK PRODUCT KEY GOES HERE!i always have it in both them places but in first it didn't work so removed and resorted to just the Run cmdsMS and their BS they don't even know how works, rely on users to figure it out in their technet forums Edited April 7, 2010 by maxXPsoft Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now