How to backup a Windows 2008 R2 KMS to prevent reactivation in case of failure?

Hi all,
I'd like to know if there is a solution to backup a Windows 2008 R2 KMS configuration to prevent reactivation of the KMS in case of reinstallation.
I just want to not being limited by the number of KMS activation with the same key.
Thx in advance for your help.

Hi,
Thanks for your posting.
You do not need to backup a KMS host.
You only need to replace the failed KMS host with a new KMS host using the same configuration and ensure that its SRV resource record is added to DNS, if you are using DNS auto-discovery. The old SRV record is deleted eventually, if record scavenging is
implemented for DNS, or you can delete it manually. The new KMS host then begins collecting renewal requests and KMS clients begin activating as soon as the KMS activation threshold is met.
Regards.
If you have any feedback on our support, please click
here
Vivian Wang

Similar Messages

How to activate Windows 8.1 on a Windows 2008 R2 KMS server when I don't have Windows 2012 R2 kms host key

I only have windows 8.1 kms host key but I can't add a client OS kms key to Windows 2008 R2 kms server. And I don't have Windows 2012 R2 license either. Is there any way I can activate Windows 8.1 using my existing kms server? Thanks.

I would like a yes no clarification answer. So does this mean that EVEN WITH THE PATCH. My Server 2012 Standard edition that currently hosts KMS VA for clients running Win7, Win 8, Office15, Server 2008, Server 2012. Will not be able to host windows 8.1?
I will have to install 8.1 and use as a host?
if you have a KMShost product key for WS2012R2, you can patch a down=level Server and be fine.
(the OP didn't renew SA or otherwise has no KMShost pkey for WS2012R2)
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)
I'm having similar issues and have a similar question that doesn't seem to be answered:
My KMS server is Windows 2008 R2 (Also is my domain controller). I want to activate Windows 2012 R2 and Windows 8.1 machines off this KMS server. I can install the 2012 R2 key just fine but receive error 0xC004F015 (The Software Licensing Service reported
that the license is not installed) when I try to install my 8.1 KMS key.
What I'm gathering from this thread is that I have to set up a Windows 8.1 host and set it up to be a KMS server exclusively for activating Windows 8.1. Is this correct? If so, Microsoft needs to fix that. I have a SERVER for activations for a reason: it
is a server, not a client. If I am mis-understanding, how do I get my Windows 2008 R2 server to accept the Windows 8.1 KMS key for activating 8.1 clients?
Thanks!
You don't need Windows 8.1 KMS key. Your 2012 R2 KMS key will be able to activate your Windows 8.1 machines. So your current set up is fine, no need to set up another Windows 8.1 KMS host.
My problem is I don't have 2012 R2 KMS key as I didn't buy any Windows 2012 R2 license. So I can't use 2012 R2 KMS key to activate my Windows 8.1.
Oh that's interesting. I guess I need to play around more because my 8.1 test machine isn't activating. I'll start a new thread for that if needed. Sorry for the confusion.

Windows 2008 R2 KMS server not activating Windows 8.1

We have a 2008 R2 server running VAMT 3.1 and with KB2757817 installed. I added our Windows Server 2012 and Windows 2012 R2 KMS product keys to the KMS host as well as our Windows 8.1 KMS key, and restarted the system.
So that when I look at the list of Product Keys I see the following keys:
Windows Server 2012 RTM ServerDataCenter;ServerStandard;ServerMultiPointStandard;ServerMultiPointPremium Volume:CSVLK
Win 8.1 RTM Enterprise;EnterpriseN;Professional;ProfessionalN Volume:CSVLK
Windows Server 2012 R2 RTM ServerDataCenter;ServerStandard Volume:CSVLK
Windows Server 2008 R2 RTM Std and Ent Volume:CSVLK (KMS_B)
Windows 7 All Volume Editions Volume:CSVLK
I then go to one of our Windows 8.1 systems and run the following commands:
cscript c:\windows\system32\slmgr.vbs /skms <servername>
cscript C:\windows\system32\slmgr.vbs /ato
and I get the following error message:
"Error: 0xC004F074 The Software Licensing Service reported that the computer could not be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information."
Meanwhile Windows 7 clients still activate without a problem.
On the KMS host I run slmgr /dlv and get the following:
Name: Windows Server(R), ServerStandard edition
Description: Windows Operating System - Windows Server(R), VOLUME_KMS_R2_B channel
Activation ID: xxxx
Application ID: xxx
Extended PID: xxx
Installation ID: xxx
Processor Certificate URL:
http://go.microsoft.com/fwlink/?LinkID=88342
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88343
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88345
Product Key Certificate URL:
http://go.microsoft.com/fwlink/?LinkID=88344
Partial Product Key: xxxx
License Status: Licensed
Remaining Windows rearm count: 3
Trusted time: 3/26/2014 9:56:25 AM
I've seen in other articles that the description should be
"VOLUME_KMS_2012-R2" channel instead of "VOLUME_KMS_R2_B channel"
My question is how do I get the 2008 R2 KMS host to activate Windows 8.1 clients?
Did I miss a step in adding the 2012 R2 KMS key, and if I did what step did I miss?

We have a 2008 R2 server running VAMT 3.1 and with KB2757817 installed. I added our Windows Server 2012 and Windows 2012 R2 KMS product keys to the KMS host as well as our Windows 8.1 KMS key, and restarted the system.
So that when I look at the list of Product Keys I see the following keys:
Windows Server 2012 RTM ServerDataCenter;ServerStandard;ServerMultiPointStandard;ServerMultiPointPremium Volume:CSVLK
Win 8.1 RTM Enterprise;EnterpriseN;Professional;ProfessionalN Volume:CSVLK
Windows Server 2012 R2 RTM ServerDataCenter;ServerStandard Volume:CSVLK
Windows Server 2008 R2 RTM Std and Ent Volume:CSVLK (KMS_B)
Windows 7 All Volume Editions Volume:CSVLK
I then go to one of our Windows 8.1 systems and run the following commands:
cscript c:\windows\system32\slmgr.vbs /skms <servername>
cscript C:\windows\system32\slmgr.vbs /ato
and I get the following error message:
"Error: 0xC004F074 The Software Licensing Service reported that the computer could not be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information."
Meanwhile Windows 7 clients still activate without a problem.
On the KMS host I run slmgr /dlv and get the following:
Name: Windows Server(R), ServerStandard edition
Description: Windows Operating System - Windows Server(R), VOLUME_KMS_R2_B channel
Activation ID: xxxx
Application ID: xxx
Extended PID: xxx
Installation ID: xxx
Processor Certificate URL:
http://go.microsoft.com/fwlink/?LinkID=88342
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88343
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88345
Product Key Certificate URL:
http://go.microsoft.com/fwlink/?LinkID=88344
Partial Product Key: xxxx
License Status: Licensed
Remaining Windows rearm count: 3
Trusted time: 3/26/2014 9:56:25 AM
I've seen in other articles that the description should be
"VOLUME_KMS_2012-R2" channel instead of "VOLUME_KMS_R2_B channel"
My question is how do I get the 2008 R2 KMS host to activate Windows 8.1 clients?
Did I miss a step in adding the 2012 R2 KMS key, and if I did what step did I miss?
It's not possible to add Windows Vista/7/8.0/8.1 KMShost pkeys into a WindowServer OS - they will not install, because the KMShost pkey must activate the host OS as well as perform KMShost functions, and, a WindowsClientOS pkey will never be accepted on
a WindowsServerOS.
Similarly, you can't install multiple Windows pkeys - only the last (acceptable) pkey will be kept - all previous pkeys will be displaced/removed (last in wins).
Your slmgr output clearly shows that you have the WS2008R2 KMShost pkey, in place. You need to install the WS2012R2 KMshost pkey to get your 8.1 KMSclients to activate.
KMShost pkeys are "cumulative", i.e. WS2012R2 KMShost pkey will activate all lower versions of both WindowsServer and WindowsClient OS.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Install Windows 2008 R2 KMS Key Error "0xC004F050 The software licensing service reported that the product key is invalid"

My KMS server is running on Windows Server 2012 R2 and activated by Server 2012 KMS Key.
I would like to use the KMS server to activate many Windows 2008 R2 server, however, Error message "0xC004F050 The software licensing service reported that the product key is invalid" is appear when adding Windows Server 2008R2 KMS Key. The Windows
Server 2008 R2 KMS key is confirmed and validated by Microsoft Telephone service.
Command used:
slmgr /ipk <Windows Server 2008 R2 KMS Key>
Anyone can help? thanks.

Hi Samson,
Based on my research, we need to choose associated KMS key based on the highest product being deployed in the product grouping hierarchy.
To choose the right Volume License key, please refer to this article:
How to Choose the Right Volume License Key for Windows
Please type the cmd "slmgr /dlv" on KMS Host and check if it has been activated successfully.
After configure KMS host, By default these KMS client computers will query DNS and locate your KMS host and activate
KMS Client Setup Keys
To reset computers to be KMS clients type the following at elevated command prompt:
Slmgr.vbs /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
Where xxxxx-xxxxx-xxxxx-xxxxx-xxxxx is the generic VL key from the following link.
https://technet.microsoft.com/en-us/library/jj612867.aspx
For more detailed information to activate KMS client, please refer to the article below:
Installing KMS Hosts
Configuring KMS Clients
If there is anything else regarding this issue, please feel free to post back.
Best Regards,
Anna Wang
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

How to connect to Windows 2008 VPN server with certificate support

Unfortunatelly if I select any Windows 2008 server compatible protocol (PPTP, L2TP) I cannot select PKI certificate, its only available for Cisco VPN. Yet my company has 1000 laptops and utilizing Windows 2008 Server for VPN (Cisco is too expensive and unnecessary because VPN is part of Windows Server). PKI certificate is required for connection security.
Any plans to enable certificates for PPTP or L2TP in 2.1 firmware? Even better would be to add SSTP protocol with certificate support, because it takes only one standard TCP connection (https) per user (uses least possible NAT resources for heavy loaded NATed WiFi spots). Also in some public places https is the only option to connect as PPTP and L2TP are filtered.

Hi Shahzad,
>>how to connect sql server 2008 r2 sp2 with visual studio 2013 ultimate?
Based on your issue, if you wan to connect the sql server 2008 r2 sp2 from VS2013 IDE. I suggest you can try the Ammar and darnold924's suggestion to check your issue.
In addition, I suggest you can also refer the following steps to connect the sql server 2008 r2 sp2 with visual studio 2013 ultimate.
Step1: I suggest you can go to VIEW->SQL Server Object Explorer->Right click SQL Server->Add SQL Server.
Step2: After you connect the SQL Server 2008 r2 sp2 fine, I suggest you can go to VIEW->Server Explorer-> right click the Data Connection->Add Connection.
And then you can create the connect string in the Add Connection dialog box.
Hope it help you!
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Windows 2012 Activation from Windows 2008 R2 KMS server

Hello,
We have 2 KMS servers in our Domain. One has server has KMS key for Windows 2012 KMS installed and other not.
I have joined first windows 2012 server to domain and its been 3 hours the server is still not activated from KMS server.
When client contacts KMS server for Windows 2012 licnese, if key is not installed on first KMS server, will it automatically contact second one? Do I need to change sonmething?
One more question:
Is it possible to have Windows 2012 key installed on the same KMS server, which is already acting as KMS sertver for Windows 2008R2? and Windows 2003 R2? or wil this cause any issues?
Mahi

Hello,
Once a KMS host is activated, it will publish it's record to DNS. KMS clients attempting to activate will query DNS to get a KMS host, if there is more than one, they will use the first one they get. The DNS server should be rotating which records
it hands out.
If they activate, they will cache that record and attempt to use it when they renew, if they fail to renew or activate, they will query DNS for the KMS host again.
Since this is a new KMS host it will need at least 5 KMS clients to contact it meet the count needs for Server.
What version of Windows is the other KMS host machine is it Windows Server 2008, Windows Server 2008 R2 or is it Windows Server 2003 R2?
Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

How to backup a SBS 2008 Server

This should be a simple question.
My concern the entire server including the exchange store.
There is a lot of conflicting information.
SO, if I used the backup wizard to backup the entire server, will I be able to restore the entire server including exchange.
Charles Frost

Absolutely, positively, affirmative. Assuming the external drive is compatible and there is a link here:
http://social.technet.microsoft.com/wiki/contents/articles/1780.windows-small-business-server-external-backup-drives-compatibility-list.aspx
And, for your reading pleasure, please review this link and the links contained therein:
http://social.technet.microsoft.com/wiki/contents/articles/1919.sbs-2011-v-backup-restore-and-disaster-recovery.aspx
You should have at least 2 targets and preferably 3. With 3, one is always out of the building. But regardless of how many, you should do a regular test restore of different items to a test folder on the server.
I have found the WD Passport Ultra to be very cost effective, comes with a three year warranty. Note that 2 TB is the largest supported target. And I have not had any issues with the ones labeled nesn.
Larry Struckmeyer[MVP] If your question is answered please mark the response as the answer so that others can benefit.

Error [0x8007007b] when backing up system state in windows backup for windows 2008 R2

running wbadmin system state results in the following error log:
Error in backup of C:\windows\\systemroot\ during enumerate: Error [0x8007007b] The filename, directory name, or volume label syntax is incorrect.
Having searched all over the web, the consensus seems to be that this error means that some service has a bad image path. I even sound a nifty powershell script that discovers services with possible problems. I fixed the problems it brought up in the registry
(there was only one), but I still get that error... I've been backwards and forwards through the list of services many times, and I don't see any problems.. Anybody got an idea??

Hi,
The issue cause by the following aspects:
1. The path incorrectly points to Windows\\systemroot\system32\drivers
2. Multiple SCSI controller drivers are being loaded at boot time and one or more is not needed. The failing SCSI controller driver is creating an issue for the WBAdmin/VSS backup process.
To resolve this issue, change the value in the registry key for
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LSI_SAS and change the Imagepath, from \SystemRoot\system32\drivers\lsi_sas.sys to System32\drivers\lsi_sas.sys
Note: After making above registry changes, the machine might not boot normally. Follow below mentioned steps to recover from the boot issue.
1. Boot the machine into Windows Recovery Environment (WinRE).
2. Open Regedit and navigate to each of the following registry keys to verify their Start values are correct.
HKLM\System\CurrentControlSet\service\LSI_FC
HKLM\System\CurrentControlSet\service\LSI_SAS
HKLM\System\CurrentControlSet\service\LSI_SAS2
HKLM\System\CurrentControlSet\service\LSI_SCSI
3. The Start value should be 0x3 for each driver that is NOT the SCSI controller driver determined earlier. Change the Start value as needed.
Values and meanings for the Start value:
0x0 = Load on boot
0x1 = System
0x2 = Auto Load
0x3 = Load on demand
0x4 = Disabled
4. Reboot the machine in normal mode.
5. Re-run the WBAdmin command, the backup should work correctly.
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Can someone tell me in simple terms how to backup or save all your songs-

on itunes-i tried to save it on a cd disc and the disc only copy 20 songs. I have almost 1700 songs on my ipod. I won't have to put my 1700 song on over 30 disc's will I?

Other options:
http://www.uneasysilence.com/how-to-backup-your-windows-itunes/
http://www.apple.com/support/itunes/musicstore/backup/
It would likely take too many CD's. Do you have a DVD burner?
JC

How to backup VM in HyperV (Windows Server 2008 R2)

Hello,
Beginner's question: How to backup my VMs on an external
USB disk?
NB: I'm running Windows Server 2008 R2. It's a test machine, don't care with downtime. I want to backup only the VM (VHD files and VM configuration, not the whole server)
Thanks

Hello,
for Hyper-V usage please ask the experts in
http://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=winserverhyperv
Also see
http://technet.microsoft.com/en-us/library/dd405549(v=vs.85).aspx
Best regards
Meinolf Weber
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog: http://blogs.msmvps.com/MWeber
Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
Twitter:

How to schedule multiple backup job through windows server backup in windows server 2008 R2

hi expert,
need your help, In my small environment I am using windows 2008 R2 as a domain controller. and installed windows server feature for backup.
Now i want to create backup at a different time.
1. System state backup at 5.00 PM on saturday only
2. finance and hr data backup on daily basis at 5.00 PM.
so how i create different job schedule through windows server backup.
Regards,
Triyambak
Regards, Triyambak

Scenario #1
The following command will create a Task Scheduler task named
DailyFolder1Backup with the start time of 23:00.
This task will run DAILY with the HIGHESTprivileges. It will run the Windows Server Backup CLI to backup
g:\folder1 to target volume
F:.
SCHTASKS /Create /SC DAILY /TN
DailyFolder1Backup /RL HIGHEST /ST 23:00/TR
"wbadmin start backup –backupTarget:F: -include:g\folder1
-vsscopy -quiet"
Scenario #2
The following command will create a Task Scheduler task named
DailyFolder2Backup with the start time of 24:00.
This task will run DAILY with the HIGHESTprivileges. It will run the Windows Server Backup CLI to backup
h:\folder2 to target volume
F:.
SCHTASKS /Create /SC DAILY /TN
DailyFolder2Backup/RL HIGHEST /ST 24:00/TR
"wbadmin start backup –backupTarget:F: -include:h:\folder2
-vsscopy -quiet"
Please feel free to let us know if you have any question or concern.
Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
the thread.

How to Delete Non-System State Backups in Windows 2008R2

Hello,
I am running a Windows 2008R2 server which uses Windows Server Backup to do the backups. We are using the backup-tool to create non-system state backups of the data-directories on this machine. The backup is done on a dedicated disk connected through iscsi
(to a Synology box). This backup disk has become too small and we have now replaced the Synology box with a bigger one. Here i created a new LUN again for the backup purposes.
Now for my question; The wbadmin.exe tool supplied with W2008R2 does not offer a way to delete the old backups. I know that in Win2012 (which we we also have running) I could add the new iscsi location and then (when enough backups are available on the new
target) use wbadmin.exe delete backup to delete the old non-system state backups; e.g.
wbadmin delete backup -version:08/07/2013-21:00
This (very undocumented) feature of Windows 2012 and higher works quite nice and is exactly what i am searching for on the W2008R2 machine; a way to delete the old backups (and under the hood delete the corresponding snapshots)
I've done quite a bit of research and it should be possible to do something similar in 2008 but then manually, The howto is described in the following link: http://blogs.technet.com/b/filecab/archive/2009/06/22/backup-version-and-space-management-in-windows-server-backup.aspx .
Basically it describes that you should use DiskShadow.exe to remove e.g. the oldest snapshot with a command like :
Delete shadows OLDEST \\?\Volume{7fc1871b-2e1f-11dd-a339-001e4fb7af35}
Windows Server backup (wbadmin) should then on the next run 'see' this deletion and update its list of available backups:
"You can perform the same steps manually to delete backups on demand. However, the backup catalog update cannot be done manually and it will happen instead during
the next backup."
I've done this on our box and it indeed removes the shadows from the list. However, in the Windows Backup 'dashboard' it still lists the backups as available. Also after a new backup has finished (according the the article this is when it should 'update'
its backup catalog). When I try to restore a backup from a date that i just removed it gives a nice message that this is impossible because the snapshot is not available (duh :)) ;
Unable to browse Local disk. The shadow copy of the backup stored on the backup destination cannot be found.
So it seems that the aforementioned method works; it removes the snapshot and frees diskspace, but it doesn't update the Windows Backup catalog. As a result the management tool (GUI) still lists the backups which are no longer available! How can i change
this? Is there any way to do this? I found one article which mentions that the Dashboard bases its screen on the Windows Logs and not on the actual VSS snapshots available:
http://forum.wegotserved.com/index.php/topic/23757-start-afresh-with-server-backup/ (WHS) In my situation however this seems unlikely because i don't have any logs that date back as far as my backups go.
In my opinion this is a real bug and it leaves us with a in-consequent backup schema. Does anyone have similar situations or even a solution to my problem?
Kind Regard, Martin

Hi Mandy,
Yes! I think i got my answer and I now get how windows backup works in Windows 2008 :-) It turns out that I dismissed some suggestions a bit too soon. The answer lies in the command mentioned earlier :
Wbadmin delete catalog
This command does delete all the backups from a perspective of the Windows Backup UI, but leaves the VSS snapshots intact. This means that the backups are still available, but you just can't restore them with the User Interface. In order to 'update' the
UI with the current available snapshots (which you can list with diskshadows list shadows all), you have to re-add the existing media on which the backups took place using the Wizard of the UI. It will then inform you that existing backups are available and
if you want to keep these for restore purposes. If you click 'yes', and THEN perform a backup ... All the current available backups will be shown in the User Interface :-)
So for my steps taken to change from one iscsi (iscsi1) to another (iscsi2):
- Add the 2nd iscsi target with the Windows Backup UI
using Backup schedule , Modify backup -> [desired options] => Add more backup destinations -> iscsi2
- Remove the 1st iscsi target with the Windows Backup UI
using Backup schedule , Modify backup -> [desired options] => Remove current backup destinations -> iscsi1
- Run some backups on the new destination. Old restore points are now still available. When enough restore points are available on the new volume iscsi2 start deleting old data from iscsi1 as follows:
- Run diskshadow
diskshadow
- list all the current snapshots
list shadows all
- remove all the snapshots of iscsi1 (repeat until all shadows are gone of iscsi1)
delete shadows oldest \\?\volume{yourvolumeid}\
- delete the windows backup catalog
wbadmin delete catalog
- Restart the windows backup UI and re-add your schedule on the new volume iscsi2. It will now ask if you want the keep the existing data for restore purposes; click yes.
- After the next backup only the backups of volume iscsi2 will be listed and everything is fine !
I Hope my post will help others with similar questions. It was quite a search before I understood the way it works. Basically as long as your VSS snapshots are still available and listed by diskshadow you still have the backups and you will be able to get
this in sync with the steps above (delete schedule and re-add originating targets containing the snapshots). After the next backup the UI will update itself.
(In my case someway along the way I lost my originating snapshots, but because I already had my new backup set it didn't bother me; It kept me from having to delete all 510 old backups :) with diskshadow)
Regard, Martin

KMS Error 0xC004F015 on Windows 2008 R2 - Does anyone have the correct fix for this please?

I am in the process of migrating my KMS server from Windows 2003 to Windows 2008 R2 64-bit. My Windows 2003 server has been happily providing my Windows 7 clients with licenses for well over a year. I have followed these migration steps in this forum article:
social.technet.microsoft.com/Forums/windows/en-US/cd4177bd-8df5-4a66-afdc-c760398b7e7f/migrating-kms-server-from-one-computer-to-another?forum=itprovistaactivation
I cannot get passed step 5. As soon as I try step 5 with my Windows 7 KMS key I receive error 0xC004F015. Despite reading countless articles on Microsoft forums and also speaking the Microsoft licensing who frankly were of no help at all, I am none the wiser
how to resolve this fault. My questions are:
1. Should my Windows 2008 R2 server be licensed with a MAK or KMS key? Does this matter?
2. Some articles I have read suggest if you use a Windows Server "C" license then you do not need to use a Windows 7 KMS key. I've tried this but it just tells me I have insufficient licenses.
3. When installing my windows 7 license key via the slmgr /ipk command should I be using my Windows 7 Professional KMS key? This works fine on my old Windows 2003 server, but Windows 2008 does not like it at all. Would I be better simply moving my KMS server
to a Windows 7 desktop instead?
4. I also want my Windows 2008 R2 to carry out my KMS activation for Office 2013. Can this run on the same server as my Windows 7 KMS key should I ever get it to work
Thank you anyone who can shed some light on this absolutely baffling error. Surely some one out there has the definitive answer.
Regards
N Buck

I am in the process of migrating my KMS server from Windows 2003 to Windows 2008 R2 64-bit. My Windows 2003 server has been happily providing my Windows 7 clients with licenses for well over a year. I have followed these migration steps in this
forum article:
social.technet.microsoft.com/Forums/windows/en-US/cd4177bd-8df5-4a66-afdc-c760398b7e7f/migrating-kms-server-from-one-computer-to-another?forum=itprovistaactivation
I cannot get passed step 5. As soon as I try step 5 with my Windows 7 KMS key I receive error 0xC004F015. Despite reading countless articles on Microsoft forums and also speaking the Microsoft licensing who frankly were of no help at all, I am none the wiser
how to resolve this fault. My questions are:
1. Should my Windows 2008 R2 server be licensed with a MAK or KMS key? Does this matter?
2. Some articles I have read suggest if you use a Windows Server "C" license then you do not need to use a Windows 7 KMS key. I've tried this but it just tells me I have insufficient licenses.
3. When installing my windows 7 license key via the slmgr /ipk command should I be using my Windows 7 Professional KMS key? This works fine on my old Windows 2003 server, but Windows 2008 does not like it at all. Would I be better simply moving my KMS server
to a Windows 7 desktop instead?
4. I also want my Windows 2008 R2 to carry out my KMS activation for Office 2013. Can this run on the same server as my Windows 7 KMS key should I ever get it to work
Hi,
on your KMShost, if that is a WindowsServer OS, you cannot use a WindowsClient (WinVista/Win7/Win8/Win8.1) KMShost product key, you must use a WindowsServer KMShost product key.
Further, the KMShost product key must match the OS of the KMShost machine (or exceed/better it).
e.g. if your KMShost machine is WS2008R2, you must use a WS2008R2 (or higher e.g. WS2012 or WS2012R2) product key.
If you will use a higher product key, you will need to install the relevant patch package to do so.
When you install a Windows KMShost product key onto a machine, the Windows KMShost product key completely replaces the previous Windows product key of that machine [it serves two purposes, (1) replace the previous key, (2) activates the KMShost feature].
So, your KMShost is neither licensed as MAK nor KMS, it becomes a KMShost.
For WS2008R2 KMShosts, you can install one of 3 types (channels/groups) of KMshost pkey.
The channel/group pkey you choose, is based upon the maximum product editions you wish to perform KMSclient activations for.
http://technet.microsoft.com/en-us/library/ff793411.aspx
For your issue #2, are you attempting to install your Windows7 KMS key upon the KMShost or a KMSclient?
For your issue #3, are you attempting this upon a KMSclient? (Volume License editions on Win7Pro or Win7Ent, are already pre-loaded with a KMSclient pkey, so you should have no need to alter the client keys). As previously mentioned, no Win7 key is needed/possible
for the KMShost, if the KMShost is WS2008R2.
For your issue #4, yes, your WS2008R2 KMShost can also act as KMShost for Office2010 and/or Office2013, this requires a further patch, and the installation of the relevant Office KMShost pkey.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

How to install SQL SERVER 2008 r2 in window 7 home premimum 64bit

how to install SQL SERVER 2008 r2 in home premimum 64bit os. can any say that weather it will support or not in window 7 home premimum os.
my server log file:
Final result: SQL Server installation failed.
To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal): -2068052700
Exit facility code: 1212
Exit error code: 1316
Exit message: SQL Server installation
failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time: 2014-03-27 00:52:25
End time: 2014-03-27
00:56:09
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL
Server\100\Setup Bootstrap\Log\20140327_005035\SSCRuntime_Cpu32_1.log
Exception help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1
Machine Properties:
Machine name: SEVALAL-PC
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance
Instance ID Feature Language
Edition Version Clustered
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER
Database Engine Services 1033 Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER
SQL Server Replication 1033 Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER
Full-Text Search 1033 Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSAS10_50.MSSQLSERVER
Analysis Services 1033 Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSRS10_50.MSSQLSERVER
Reporting Services 1033 Standard Edition 10.50.1600.1 No
Sql Server 2008 SEVALAL MSSQL10.SEVALAL
Database Engine Services 1033 Express Edition 10.3.5500.0
No
Sql Server 2008 SEVALAL MSSQL10.SEVALAL
SQL Server Replication 1033 Express Edition 10.3.5500.0
No
Sql Server 2008 R2
Client Tools Connectivity 1033
10.50.1600.1 No
Sql Server 2008 R2
Client Tools Backwards Compatibility 1033
10.50.1600.1 No
Sql Server 2008 R2
Client Tools SDK 1033
10.50.1600.1 No
Package properties:
Description: SQL Server Database Services
2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 0
Installation location: G:\01.SQL Server 2008 R2 FullVersion\x64\setup\
Installation edition: STANDARD
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: <empty>
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup
Bootstrap\Log\20140327_005035\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: True
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: IS,SSMS,ADV_SSMS,OCS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: *****
HELP: False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL
Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft
SQL Server
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\SYSTEM
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: <empty>
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: <empty>
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: True
TCPENABLED: 0
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup
Bootstrap\Log\20140327_005035\ConfigurationFile.ini
Detailed results:
Feature: Integration
Services
Status: Failed:
see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management
Tools - Complete
Status: Failed:
see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management
Tools - Basic
Status: Failed:
see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Microsoft Sync
Framework
Status: Failed:
see logs for details
MSI status: Passed
Configuration status: Passed

my summary log file information:
Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal): -2068052700
Exit facility code: 1212
Exit error code: 1316
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time: 2014-03-27 00:52:25
End time: 2014-03-27 00:56:09
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140327_005035\SSCRuntime_Cpu32_1.log
Exception help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1
Machine Properties:
Machine name: SEVALAL-PC
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Database Engine Services 1033
Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER SQL Server Replication 1033
Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Full-Text Search 1033
Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSAS10_50.MSSQLSERVER Analysis Services 1033
Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSRS10_50.MSSQLSERVER Reporting Services 1033
Standard Edition 10.50.1600.1 No
Sql Server 2008 SEVALAL MSSQL10.SEVALAL Database Engine Services 1033
Express Edition 10.3.5500.0 No
Sql Server 2008 SEVALAL MSSQL10.SEVALAL SQL Server Replication 1033
Express Edition 10.3.5500.0 No
Sql Server 2008 R2 Client Tools Connectivity
1033 10.50.1600.1 No
Sql Server 2008 R2 Client Tools Backwards Compatibility
1033 10.50.1600.1 No
Sql Server 2008 R2 Client Tools SDK
1033 10.50.1600.1 No
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 0
Installation location: G:\01.SQL Server 2008 R2 FullVersion\x64\setup\
Installation edition: STANDARD
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: <empty>
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140327_005035\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: True
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: IS,SSMS,ADV_SSMS,OCS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: *****
HELP: False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\SYSTEM
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: <empty>
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: <empty>
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: True
TCPENABLED: 0
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140327_005035\ConfigurationFile.ini
Detailed results:
Feature: Integration Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Complete
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Microsoft Sync Framework
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140327_005035\SystemConfigurationCheck_Report.htm

How to back up Windows 2003 R2 and restore it on Windows Server 2008 R2?

Hi,
I have an old server running on Windows 2003 R2 Standard OS. It has file server and application server roles. No AD domain services. It has 1TB of data as well.
I'd like to replace the server with new hardware with Windows 2008 R2 Standard installed.
I'd like to know the steps. what to and how to backup Windows server 2003 R2 and restore it on 2008 R2.
Thanks in advance.
Joe

Here are some useful links to reference
https://technet.microsoft.com/en-us/library/dd379511(WS.10).aspx
https://technet.microsoft.com/en-us/library/ff972408%28v=ws.10%29.aspx
You should be able to upgrade the OS directly from 2003 R2 to 2008 R2
I would recommend backing up the information with backup assist or creating a system state backup via windows first before attempting anything. I know BackupAssist will allow you to back up all your information and restore it with the same permissions
to any server.

How to backup a Windows 2008 R2 KMS to prevent reactivation in case of failure?

Similar Messages

Maybe you are looking for