+ Post New Thread
Page 3 of 3 FirstFirst 123
Results 31 to 37 of 37
Windows 7 Thread, Windows 7 Imaging WDS Woes in Technical; The issue is that I still don't see a volume but I have reached the sysprep limit so I can't ...
  1. #31

    witch's Avatar
    Join Date
    Nov 2005
    Location
    Dorset
    Posts
    11,044
    Thank Post
    1,315
    Thanked 2,308 Times in 1,623 Posts
    Rep Power
    692
    The issue is that I still don't see a volume but I have reached the sysprep limit so I can't even try to inject the drivers until I can sysprep it again. The reg key didnt work.

  2. #32


    Join Date
    Mar 2009
    Location
    Leeds
    Posts
    6,505
    Thank Post
    227
    Thanked 848 Times in 727 Posts
    Rep Power
    287
    what happens if you boot of a win7 dvd does that find the hdd as a valid install location or does that also show no drives?

    what pc is it i will see if i can hunt round and make you a new boot.wim. easiest way to test that is use the ms tool to create a win7 install pen drive (requires a 4gb+ pendrive) and then swap teh boot.wim file in the pendrives sources folder for a new one see if that finds the hdd as a valid install location
    Last edited by sted; 26th April 2011 at 08:45 AM.

  3. #33

    Join Date
    Dec 2008
    Location
    Essex
    Posts
    2,137
    Thank Post
    1
    Thanked 326 Times in 316 Posts
    Rep Power
    77
    @witch

    In your unattend.xml file under the section Microsoft-Windows-Security-Licensing-SPP component, set SkipRearm to 1 then save this. Then try to sysprep again. If you plan to sysprep /generalise more than 3 times, then you have to set this setting to bypass the activation clock. Also, ensure the reg key is set.

    Can you also check %WINDIR%\System32\Sysprep\Panther directory for any log files such as seterr.log and post/PM.


    Sukh

  4. #34

    Join Date
    Dec 2008
    Location
    Essex
    Posts
    2,137
    Thank Post
    1
    Thanked 326 Times in 316 Posts
    Rep Power
    77
    @witch

    In your unattend.xml file under the section Microsoft-Windows-Security-Licensing-SPP component, set SkipRearm to 1 then save this. Then try to sysprep again. If you plan to sysprep /generalise more than 3 times, then you have to set this setting to bypass the activation clock. Also, ensure the reg key is set.

    Can you also check %WINDIR%\System32\Sysprep\Panther directory for any log files such as seterr.log and post/PM.


    Sukh

  5. #35

    witch's Avatar
    Join Date
    Nov 2005
    Location
    Dorset
    Posts
    11,044
    Thank Post
    1,315
    Thanked 2,308 Times in 1,623 Posts
    Rep Power
    692
    Quote Originally Posted by sukh View Post
    @witch

    In your unattend.xml file under the section Microsoft-Windows-Security-Licensing-SPP component, set SkipRearm to 1 then save this. Then try to sysprep again. If you plan to sysprep /generalise more than 3 times, then you have to set this setting to bypass the activation clock. Also, ensure the reg key is set.

    Can you also check %WINDIR%\System32\Sysprep\Panther directory for any log files such as seterr.log and post/PM.
    I did try this but it didnt work last time. I will try again tomorrow when I am in the right school

  6. #36

    Join Date
    Feb 2008
    Posts
    8
    Thank Post
    1
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    This might be useful, as it is detailed instructions on how to reset the rearming to 1, then the above skip rearm would not increment.

    Reset your Rearm count, run Windows 7 Forever without cracks

  7. #37


    Join Date
    Feb 2007
    Location
    51.405546, -0.510212
    Posts
    8,706
    Thank Post
    220
    Thanked 2,615 Times in 1,926 Posts
    Rep Power
    777
    Once you have gone over the SysPrep limit, SkipRearm will no longer work from what I can tell.

    Typically while creating a deployment image, you will run the Sysprep command multiple times. To ensure that an installation of an image receives the full Activation grace period:
    1. Set the SkipRearm to 1 while customizing your computer.
    2. Before running the Sysprep command the final time before deploying an image, rearm the computer by setting the SkipRearm setting to 0. This resets the Activation grace-period timer.

    You can review the number of times you can use the SkipRearm setting by running the Slmgr.vbs /dlv command.

    Values
    0 = Specifies that the Windows licensing state will be restored to the original, out-of-box licensing state, and that licensing settings are restored to their defaults. This is the default value.
    1 = Specifies that the Windows licensing state will not be changed. The Activation grace-period timer is not reset.

SHARE:
+ Post New Thread
Page 3 of 3 FirstFirst 123

Similar Threads

  1. Windows 7 and Imaging
    By dhorowitz in forum Windows 7
    Replies: 20
    Last Post: 14th August 2013, 10:19 PM
  2. [WDS] WDS hangs when imaging laptops
    By rkoufii in forum O/S Deployment
    Replies: 5
    Last Post: 3rd September 2012, 09:27 PM
  3. WDS - XP imaging
    By bodminman in forum O/S Deployment
    Replies: 6
    Last Post: 10th December 2010, 02:28 AM
  4. [Windows Software] Deploying Windows 7 Professional using WDS into Windows 7 OEM licensed workstation
    By albertwt in forum Licensing Questions
    Replies: 2
    Last Post: 29th July 2010, 07:26 AM
  5. Imaging Windows 7
    By Newton in forum Windows 7
    Replies: 3
    Last Post: 18th November 2009, 10:33 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •