Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 377
  • Last Modified:

RIS windows activation problem/s - help

After successfully implementing RIS and getting it to install images on PCs successfully I have come across two annoying problems.

-I am unable to activate the product over the internet (will activate using phone method) I created the image using a OEM copy of windows which came preinstalled/activated on a new HP laptop. I removed unwanted HP apps and installed the apps I required for my image then browsed to the RIMNST directory and ran RISETUP which ran through and worked fine. I then did a PXE boot on a laptop (exactly the same model) and installed from the image I created this all works fine. Once finished I get the mini setup where I enter the OEM xp licence key from the bottom of the laptop, it accepts it and its done.
but
when I get the activation notification I choose to activate over the internet and not to register at this time then it just hangs on checking for connectivity and does not activate (I can call up and do the phone activaion fine and I have a working internet connection). there is also no option to attempt to activate windows eg all programs\activate windows or accessories\activate windows, I have to reboot to get prompted to activate windows again and the same thing happens over and over.

problem two.
In the image I created initially I have VMware installed and the VM machine files are located in the all users\shared documents directory, after installing the image on a PC via RIS VMware works fine but the VM files for the machines (NT and 98) in the shared doc directory are there but the size is 0 KB and obviously they dont work....any ideas

anyhelp much appreciated
0
Tonywbb
Asked:
Tonywbb
1 Solution
 
Netman66Commented:
RIS isn't really meant to deploy OEM builds like this.

You should be using Volume media with a Volume key.  It's not legit to distribute OEM builds in this way (check the license).

As for Activation, did you run RIPREP?  A currently activated product that is reimaged will cause significant grief - as you've found out.

Best bet - do not activate the original machine, strip out the pre-loaded stuff then RIPREP it.

I think you're going to find out that, even though the hardware is the same, the MAC and UUID's of the other components are different enough to interfere with re-activation of a previously activated machine.

With respect to the Shared folder contents - change the VM's to a folder directly off the C:\ drive.  The Shared folders is not appropriate for maintaining files that are to be included in the image.

0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now