When using the Reinstallation DVD from Dell it grabs the license key somewhere on the computer. We bought our Dell computers with Windows 7 Pro and we don't have a volume license. I was wondering if I can configure Sysprep to duplicate this so we won't need to manually type in the license key from the sticker. 
 
  
Thanks in advance.

Answer Summary:
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

2

I'm pretty sure if you leave in out of your answer file then it should auto activate it. I can't test that currently, but I seem to recall doing it that way before.

Answered 07/23/2012 by: dugullett
Red Belt

Please log in to comment
2

did some digging for:The reason why we can't PXE is because we have two k2's on our network for two seperate buildings and two different IT departments. We have been trying for years to seperate them from us but unfortunently I don't think it'll ever happen. When I PXE boot I automatically connect to their K2. KBE manipular lets me set the IP for the K2 I want to connect to.

and you can try using the KBE manipulator to force the ip for the kbox you want.

The address is set by this in Kace's scripts

@echo.

 

@echo *** Locating K2000 IP address from DHCP option 66 or 244

 

kgetdhcp 66 > %TMP%\kbox-ip-address

 

if errorlevel 1 kgetdhcp 244 > %TMP%\kbox-ip-address

 

@if errorlevel 1 (

 

@echo.

 

@echo ERROR: Unable to determine server IP address from DHCP

 

@echo WARNING: Using hardcoded IP address as fallback

 

@echo > %TMP%\kbox-ip-address

 

)

 

set /p KBOX_IP=<%TMP%\kbox-ip-address

 

@if "%KBOX_IP%"=="no data" (

 

@echo.

 

@echo ERROR: Unable to determine server IP address

 

exit /b 1

 

)

 

@if "%KBOX_IP%."=="." (

 

@echo.

 

@echo ERROR: Unable to determine server IP address

 

exit /b 1

If you add below using the KBE manipulator

set /p kbox_ip=x.x.x.x (your kbox ip)

It should then force it to your ip with the boot disks/usb sticks since the user additions get placed after this part of the script.

Answered 07/23/2012 by: SMal.tmcc
Red Belt

  • if this does not work I can give you a net use command to remap y from there server to yours.
  • I did some thinking and both kbox's will need the same admin PW for this to work, if that is not possible I can give the net use command to remap y: from the one kbox to yours..
Please log in to comment
1

Sysprep will not work, you will pick up the key from the master and deploy it to all targets.  The DVD works because it is only one machine.  You would need to read the existing key from the target key prior to deployment.

Answered 07/23/2012 by: SMal.tmcc
Red Belt

  • Wow now I don't know how I'm going to do this. We don't have control over our DHCP so I can't PXE boot but I asked them to reserve 5 IP addresses for deployment. I have created 5 different KBEs with 5 different static ip addresses thanks to KBE Manipulator. I have burned 5 CD's and what I end up having to do is go to individual machine and boot from the CD.

    Sorry I'm kind of new at this whole thing. What would be the best thing to do? I'll be using the same IP address again and again right after it grabs the image. There will be no IP conflict because the image is set to automatically grab an IP address I just need the static IP to connect with the K2.
  • New question? If the computers are already on the network and you are reimaging they should use the same IP that is assigned to them in windows since this goes by the MAC not the OS. The only big thing should be to see if your network techs have enabled options 66 and 67 on the network(s) you are pxe booting from. Also did you see dugullett's ans on the key.
  • The reason why we can't PXE is because we have two k2's on our network for two seperate buildings and two different IT departments. We have been trying for years to seperate them from us but unfortunently I don't think it'll ever happen. When I PXE boot I automatically connect to their K2. KBE manipular lets me set the IP for the K2 I want to connect to.
  • You should be able to put two K2000's out there. Make sure you do not advertise your DHCP options 66 and 67 at the server level, do this at the subnet level. This allows you to put different option 66 IP depending on the subnet you are on. To avoid DNS interference use the IP of the Kbox2000 for your option 66. Make sure no IP helper or forwarders are pointing to the other server also
Please log in to comment
1

did find this on a MS forum

 

AFAIK, it's either impossible or highly impractical to use an OEM License with an MSDN DVD, mainly because the OEM key follows a different key hashing algorithm and pings a different server than a retail or MSDN license. In other words, the OEM license goes with an OEM DVD, and ditto for the retail/MSDN version.

Answered 07/23/2012 by: SMal.tmcc
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity