Windows / Office Licencing



  • The majority of our images in district are Windows 7 with MS Office 2016. I’m curious if their are any work arounds on Windows license activation after image. I do not use sysprep as I make an image per each iteration of hardware in our district.

    Currently, I allow FOG to register host on domain. Then I log in each machine and register each machine on the internet with MS. We have volume licensing.

    I mentioned setting up a license server to the senior admin in the district but he wasn’t too thrilled with the idea.

    Any suggestions would be helpful!

    I’m trying to shave every second off of this process as I can while still keeping it simple!

    Cheers,

    Joe Gill



  • @gnoetzel

    We are using Office 2016.

    So I went through all of what is listed here before and what I ended up doing was activating said office on pre-image. Then sysprepping. After I pushed the new image, office will prompt you to setup update service and licence on first use. It will licence as normal over the internet.

    It’s still not the best solution, but… Until 2016 has KMS licence available, this is what I’m doing.

    Good luck!!

    Joe


  • Moderator

    @gnoetzel Make a new image with MS Office unactivated, and use that. Others may have better advice, so stay tuned.



  • I have 8 computers that have ‘pre-install’ MS Office 2016. I have separate keys for each machine. However, I used FOG to image 1 computer that was already activated.
    When I re-image another computer - I was not able to use Office since the Key already used and could not be activated.
    I tried Repair Office - and it was cumbersome and I don’ think doing the repair would work on the 3rd computer.
    Does the CSCRIP if put into FOG Snapin - work during the imaging?
    MS Office 2016 requires activation via internet with a user name/password.

    I appreciate everyone suggestions or recommendations.

    thanks



  • @george1421

    Thanks!! You have been very helpful!


  • Moderator

    @Joe-Gill This script will activate office 2010. You will need to adjust the path for office 2016 and for system arch (x64 or x86). You can just create the vbs script and deploy as a snapin or if you are creative you can package with the office 2016 snapin, or use the office setup took and just add the key into the setup configuration and let office do that.

    cscript “c:\program files\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform” ospprearm.exe
    cscript “c:\program files\Microsoft Office\Office14\ospp.vbs” /inpkey:[Office KMS Key]
    cscript “c:\program files\Microsoft Office\Office14\ospp.vbs” /sethst:[IP Address]
    cscript “c:\program files\Microsoft Office\Office14\ospp.vbs” /act


  • Moderator

    @Joe-Gill said in Windows / Office Licencing:

    How about MS Office activation? Is their anyway to automate that?

    Powershell snapin that runs activation for you. If you associate a snapin with a host, that snapin will run automatically after every imaging task on said computer.



  • How about MS Office activation? Is their anyway to automate that?

    @Developers FYI The Trunk ver. of the client works like a charm for Windows Activation! Thanks!!! You guys rock!



  • @george1421

    Thanks for the explanation. I come more from a Unix / Linux background where licensing is simpler. :-) We use MAK for certain. We do not have KMS set up here.


  • Moderator

    @Joe-Gill The actual keys used doesn’t matter for your task at hand. The systems activate the same way. The MAK vs KMS is part of your internal IT governance process (license management).



  • We must use KMS. The keys we have we can re-use until the pool fills up. Then you have to release some. I’ll have to ask the other admin. Thanks!


  • Moderator

    @Joe-Gill said in Windows / Office Licencing:

    @Wayne-Workman

    Do the images need to be sysprepped in order to go the FOG client route?

    Nah. You’re good to go.


  • Moderator

    @Joe-Gill Understood.

    Just realize that MAK keys are churn and burn (i.e. you only get one activation per MAK key and those key’s (license) can’t be reclaimed if you dispose of the hardware. They are a one time use key). With KMS keys when you dispose of a system the KMS key returns to the license pool.

    No sysprep is not required for the FOG client.



  • @Wayne-Workman

    Do the images need to be sysprepped in order to go the FOG client route?



  • @george1421

    I’ll keep that in mind. I’m going to try the Trunk option that Wayne mentioned first.

    No KMS here. I’m assuming it’s MAK. I’m the new guy still so I’m learning as I go.

    Thanks!!

    Cheers,

    Joe Gill


  • Moderator

    I should add that the fog client activates windows fine with MAC keys, as far as I know.

    KMS is a different animal, and I’ve not tested it what-so-ever with the new client. For KMS, I’d go George’s route.


  • Moderator

    @Joe-Gill Really You didn’t mention if you were using MAK or KMS keys. But most places will use a KMS key server since all of the licensing is done locally (without the client computers having direct access to the internet). The KMS server also allows you to revoke keys and upgrade/downgrade activation.

    But to answer your question you can create a setupcomplete.cmd and put the following lines in it.

    cscript “C:\Windows\System32\Slmgr.vbs” /ipk [Windows KMS Key if not already in your image]
    cscript “C:\Windows\System32\Slmgr.vbs” /ato

    That will activate the workstation after setup has complete and before the first logon happens.

    If you have a local KMS server insert the following command between the two above.
    cscript “C:\Windows\System32\Slmgr.vbs” /skms [IP_Address]
    cscript “C:\Windows\System32\Slmgr.vbs” /ato

    This code should be executed on the target computer not your reference image.



  • @Wayne-Workman

    Awesome!! I like that!! That’s what I did with our AD and it worked perfectly! :-)

    Thanks!!!

    Man, I’m going to owe all you guys/gals in the FOG project a beer!

    Cheers,

    Joe Gill


  • Moderator

    @Quazz In 8.1 and later, windows becomes un-activated when it detects it’s hardware UUID changed. MS Office is the same way now.


  • Moderator

    If it’s a volume license, isn’t it possible to simply capture after activation? Or does Microsoft not like that?


Log in to reply
 

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.