Jump to content


Established Members
  • Posts

  • Joined

  • Last visited

Posts posted by charles

  1. Client


    Microsoft ® Windows Script Host Version 5.8
    Copyright © Microsoft Corporation. All rights reserved.

    Software licensing service version: 6.1.7601.17514

    Name: Windows® 7, Professional edition
    Description: Windows Operating System - Windows® 7, VOLUME_MAK channel
    Activation ID: 9abf5984-9c16-46f2-ad1e-7fe15931a8dd
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 55041-00172-007-174153-03-1033-7601.0000-1542014
    Installation ID: 004132561416519403578295156233172955014925186024976125
    Processor Certificate URL: http://go.microsoft....k/?LinkID=88338
    Machine Certificate URL: http://go.microsoft....k/?LinkID=88339
    Use License URL: http://go.microsoft....k/?LinkID=88341
    Product Key Certificate URL: http://go.microsoft....k/?LinkID=88340
    Partial Product Key: VJ6Y3
    License Status: Licensed
    Remaining Windows rearm count: 2
    Trusted time: 17/03/2015 09:45:28


    Are you injecting a MAK product key while syspreping?


    It should read: Description: Windows Operating System - Windows® 7, VOLUME_KMSCLIENT channel


    And then it would work as expected...


    Change the key with the /IPK command and then /ato and it should register with no problems.

  2. Hi,


    Let me firts explain how i inherited this:


    I have a TS in sccm 2007R3 that deployes windows 7 and does the following in the bitlocker steps on standalone laptops(not domain joined after ts finishes):

    ( password and tpm already activated and set in bios with cctk tools)


    Bitlocker step:

    1. manage-bde -tpm -turnon

    2. reboot

    3. (depending on the laptop model we must manualy press "y" to activate the tpm. In our case fujitsu laptops S781. for our dell laptops this is not requierd)

    4. manage-bde -tpm -takeownership <password>

    5. manage-bde -protectors -add c: -tpmandpin <password>

    6. default enabel bitlocker step with default values(recovery key in ad etc )


    Bitlocker policy's are set via localgpo tool before bitloker step.


    This all works for new deployments.


    When reimaging these standalone laptops steps 1-4-5 fail because this has already been set.



    1. Is this the best way to do this?

    2. Does the tpm ownership get wiped when laptops are reimaged or is this the same password?

    3. Can u use the same recovery key from AD or is there a new one generated every time we reimage a laoptop?

    3. Is it needed to take ownership for tpm?


    Keep in mind that after these laptops are imaged, users must logon with pin number and users must not be able to change bitlocker or tpm ownership/keys.


    thanks in advanced for ur help.



  • Create New...