Questions[kms](server)

I have cloned and deployed several PCs with similar hardware as they are of the same model.

The steps are as follows:

Computer A:

1. Install Windows
2. Install applications/drivers/updates
3. Capture Image Version #1
4. Run sysprep
5. Join domain
6. Activate windows and office

Computer B, C and so on:

1. Deploy Image Version #1 to a machine
2. Run sysprep
3. Join domain
4. Activate windows and office

Run the following bat file when sysprep

@ECHO OFF
reg add "HKLM\SYSTEM\Setup\Status\Sysprepstatus" /v CleanupState /t REG_DWORD /d 00000002 /F
reg add "HKLM\SYSTEM\Setup\Status\Sysprepstatus" /v GeneralizationState /t REG_DWORD /d 00000007 /F
reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform" /v SkipRearm /t REG_DWORD /d 00000001
msdtc -uninstall
timeout 120
msdtc -install
timeout 120
rmdir /Q /S "C:\Windows\System32\Sysprep\Panther" 
del /Q "C:\Windows\System32\Sysprep\Sysprep_succeeded.tag "
ECHO Beginning Sysprep. The system will shutdown when complete.
"C:\Windows\System32\Sysprep\Sysprep.exe" /oobe /generalize /shutdown

I have now realised that windows and office fails to activate on the kms server by itself. Any idea on how I can remedy the problem. Thanks.

What is the difference if I sysprep /generalize with SkipRearm=1 and sysprep /generalize with SkipRearm=0?

How can I activate Windows 10 clients via an existing KMS Server running on Windows 2008 R2?

EXISTING ENVIRONMENT

• Windows 2008 R2 Server running the KMS Host role
• Existing KMS key is Windows 2012 R2 (or lower) installed on the KMS host from a previous setup.
• Current activations are fine for Windows 2012 R2 and lower on servers, and Windows 8.1 and lower for clients.

DESIRED OUTCOME

• Activation of Windows 10 clients via the KMS host

I'm using Cloudfront with an S3 origin that is using KMS to encrypt objects. I'm getting the following error when sending a GET request for an object in the S3 bucket.

Requests specifying Server Side Encryption with AWS KMS managed keys require AWS Signature Version 4.

I assumed Cloudfront would be smart enough to use AWS Signature Version 4 when requesting the object, but perhaps not?

It looks like this has been an issue with new S3 regions. Amazon recently added support for these new regions but I don't think they have addressed the issue with KMS-encrypted objects.

Does anyone have experience with this and know if there is a way to get Cloudfront's origin access identify to use signature v4?

I have 3 windows 2012 R2 servers that our sys admin guys are having trouble getting to talk to our KMS server properly.

I'm sure in time they'll work out whatever issue they're having since we're properly licensed - but I'm wondering in the meantime how much of a grace period I have on these servers, and what happens after that grace period expires? I couldn't really find any concrete info for 2012 R2 - will it throttle the number of connections or put in place other limitations?

Windows 2012 is registering/licensing ok so depending on the grace period / consequences I may just go with that.

What are the differences (and maybe pros and cons) of KMS and MAK license activation for Windows 7?