Windows 2008 R2 OEM to Volume License change after p2v.

Did online search and even called Microsoft licensing, got very confusing and different answers. So posting here.
P2V'd a HP server running 2008 R2 Standard (64 Bit) , everything went smooth, after 2 weeks server is giving "Build 7601, the copy of windows is not genuine. The Product ID reads : 00XXX-OEM-8XXXXXX-1XXXXX
Our company does have volume license keys and my understanding is that we need to give one to this server. Can I just change product key and activate using new volume licensing key ? or do you I need to do a repair- as I read in most cases with win2003.
Called MS:
1st Support Agent : Go ahead, change product key, reboot and give us a call to reactivate.
I asked for another confirmation and was transferred to tech support
Tech Support: Give us your name, number etc., we need to open a ticket, charge $259 or let me transfer you to volume licensing.
2nd Support Agent: We recommend a clean install for any volume licensing changes. Kept repeating it x 10.
me: This is a production server, I cannot do that, its too late, sorry.
he: Ok, then go ahead and try to change the key and see if it works.
me: would it break anything or any risk
he: Not sure, as we recommend a clean install is recommended for any Volume License.!
Please advise if anyone has come across upgrading OEM to Volume after p2v. thanks

Hi Karma,
For the license issue after P2V, the thread may be helpful for you:
Licensing OEM servers after P2V
In addition, if you have further concerns about licensing, I still recommended to contact
Microsoft Licensing specialist for better assistance.
Best Regards,
Anna Wang
Thanks for your suggestions. But the threads are too long to read for a simple problem with a simple solutions.
Here is the solution for anyone looking, Please check you license key sticker and there should a Virtual Key just below the OEM , use that key after migration. and you are GOLD!
Unfortunately, two of the Microsoft Licensing Specialist I spoke to, had no clue about this.

Similar Messages

Converting Standard 2012 r2 open volume license to Standard 2008 r2 sp1 open volume license

I have 2 Standard 2012 r2 open volume license's. I wish to convert them to Standard 2008 r2 sp1. I am presently logining into Microsoft Licensing Service Center and have pulled the product key for the 2008 r2 sp1 server. The license ID
is my open volume license ID. I know I put this into the product number upon installtion. What needs to be done next for activation.

Hi
If you have Windows Server 2012 Standard edition,you will have the right to downgrade your bits to any prior version of Enterprise,Standard or Essentials editions.
MS Article;
http://download.microsoft.com/download/4/D/B/4DB352D1-C610-466A-9AAF-EEF4F4CFFF27/WS2012_Licensing-Pricing_FAQ.pdf
Follow these steps to downgrade to a previous version of Windows Server Software
1.Obtain genuine Windows media and corresponding product key for the version of Windows that is eligible for downgrade.
The media should come from a prior legally licenced version from the OEM or Retail channels.
End users WHO are licensed separately through Microsoft Volume Licensing (VL) may provide their VL media and key to a system builder to facilitate the downgrade on their own systems.
2.Insert the downgrade-eligible version of Windows media in the CD drive and follow the installation instructions.
3.Type the product key.
If the software was previously activated,you will not able to activate it online,In this case.the appropriate local Activation Support phone number will be displayed.Call the number and explain the circumstances.When it is determined that end user has an
eligible Windows licence,the customer service representative will provide a single-use activation code to activate the software.Please note that Microssoft does not provide a full product key in this scenario.
4.Activate the software.

Rebuilding OEM device with Volume License image

Hello,
I built a Windows 8 Pro device with Volume License media to allow people in the organisation to evaluate but now I want to return this to its original state so it can be given to charity.
I have tried rebuilding this using a default media VL USB stick but it doesn't seem to be able to pick up the OEM product key that I assume is stored in the BIOS.
Do I need to rebuild this device using OEM/Retail media for it to detect the built in key or is there another way to do this using the VL media I already have?
Many thanks,
Tony

Ahh OK that makes sense. Thanks for clearing that up guys.
I am sure a recovery partition was there before I rebuilt it but in theory then, does this mean if I rebuilt this using OEM or Retail media of the same edition it would pick up the product key or is it coded to only recognise OEM media from the
actual manufacturer of the hardware?
I know with Windows 7 you can happily use an OEM key with retail media and vice versa as long as the edition is the same - does anyone know if this is the case with Windows 8?
It would be good to know for future reference.

Windows 8.0 Volume License machines reboot and windows 8.1 is installed??

We are a small private university with 484 computers running Windows 8.0 with MAK key.
This week we have had 2 Windows 8.0 computers spontaneously upgrade to Windows 8.1.
Since we do have a windows 8.1 MAK key all we had to do was enter the correct key and the computers were fine but everything I am reading about Volume Licensing says that this is not an upgrade path for Windows 8.1.
Is Microsoft pushing out Windows 8.1 slowly to volume licensed computers on Windows 8.0, or is this just some sort of anomaly that may happen occasionally.
One of our operators reported that the usual blue banner prompting upgrade appeared the day before but did not have an option on the banner to deny the upgrade. The next morning when she booted the computer, Windows 8.1 installed and we had to enter
the 8.1 MAK key and all appears to be well.
This is not really a complaint, just that we were VERY surprised when it happened, hoping it was not some sort of hack by a third party.
Jim Smith[REMOVED]
Lubbock Christian University
Technology Services
[removed]

Hi,
I don't know how useful this information will be for that many machines. This was also observed on 8.1 Pro, not Enterprise, but here is what I found while doing multiple different upgrades... just so I could figure out how to stop them...
Windows Update KB2973544 triggers Win 8.1 to automatically install.
http://support.microsoft.com/kb/2973544
In addition, KB3008273 appeared in Nov. 2014, which is also related to the automatic installation of Win 8.1... It actually replaces KB2973544.
http://support.microsoft.com/kb/3008273
Windows Update KB2871389 makes Win 8.1 available in the Store, and is a prerequisite for KB2973544 and\or KB3008273. You might uninstall it also.
https://support.microsoft.com/kb/2871389/en-us
I have found that the installation of KB2973544 and\or KB3008273 create Scheduled Tasks in Task Scheduler under *** Microsoft \ Windows \Setup***
They are...** 8.1 Auto Install Ping** and **8.1 Auto Install V2**. They are scheduled for 8pm Daily.
I clicked on both and selected "RUN", as I didn't want to wait several hours to see what happened... A download started immediately.
After downloading for about an hour, I restarted the machine to see what would happen... The download resumed quickly after the restart.
After the download started again, there were two more Scheduled Tasks added to the same location....   **Windows AutoUpdate Setup Resume Task**... which was running, and
**Windows AutoUpdate Setup Store Resume Task**... which is *Ready*, but has NEVER run.      There was a Service *Modern Setup Host* running in Taskmanager.
***I have found that the only way to stop the installation of Win 8.1 once the Scheculed Task ....   **Windows AutoUpdate Setup Resume Task** is indicating "At Logon" for it's Trigger,
is to end all the tasks showing, starting with that one, and then the ** 8.1 Auto Install Ping** and **8.1 Auto Install V2**.
After Ending the tasks Delete them...
After deleting the Tasks, I had to go to C:\ $Windows.~BT, which is a Hidden File, and delete anything that has a recent date... especially the .esd file (Install.esd) of 2.67GB..
I deleted anything that was newer than one week. You could probably delete everything inside the *Sources*, *Support*, and *Drivers* folders...
Also uninstall the mentioned KB's, starting with the newest, and doing the KB2871389 last, as it requires a reboot.
Any attempt to reboot the machine before doing this results in the installation of Win 8.1 starting...
If you were to End the tasks and disable or delete them while the **Windows AutoUpdate Setup Resume Task** is still showing a
Date and Time for it's trigger, deleting the $Windows.~BT files may not be necessary.
The biggest issue with this process is that you may be denied access to the $Windows.~BT folder. If that is the case, you will need to take Ownership of it.
If you disable and delete the Scheduled Tasks, and uninstall the previously mentioned KB's shortly after selecting *Remind Me Later*
THE FIRST TIME, the process will be stopped, and it won't be necessary to delete anything in the $Windows.~BT folder.
You should have about 24 hours to do this.
After uninstalling the KB's and deleting the scheduled tasks, a new scheduled task has appeared.
It is *Pre-Staged GDR Notification*, and is scheduled to run at *8PM of Every Thursday of Every Week*. My guess was that this is to remind you to install the Win 8.1 Update.
It actually causes another task to be created... *Windows Upgrade Notification Task*... It runs at the *Log On of Any User*
I couldn't get this task to show a notification. The task ran when I did it manually, but generated an error message in the log... *Specified Module Could Not Be Found (0x8007007E) Windows Upgrade Notification*
This is most likely because the KB's have been uninstalled.
I'm sure they can be disabled as well, if you want to stop\prevent the reminders.
I know that once Win 8.1 Update actually installs, those scheduled tasks no longer exist. In fact, the entire SETUP folder disappears.

Windows 8 Pro volume license version does not have "Add Features" therefore cannot install media center.

As the title describes, Windows 8 Pro installed from the Volume License ISO does not have the Add Features wizard, and as such it appears to be impossible to install the Windows Media Pack.
I've consulted with Live Chat support who cannot provide an answer to this, they simply said it should be done through "Add Features" which does not exist.
A similar thread was answered by saying install from a Retail disc and upgrade. However this is hardly a solution, paying for an additional Windows license when you already have a volume license.
Can anyone, preferably MSFT, provide a proper answer on how Windows Media Center can be install on Windows 8 Pro which is volume licensed. If it can't be done can some reason or justification be given as to why it can't be done.
Please see previous thread here: http://social.technet.microsoft.com/Forums/en-US/w8itproinstall/thread/d63b46e5-c542-4dbe-be41-c46cda440723

I would like to pile on here and say "ditto" to all of the above. you have a licensed product and they don't even support the MSFT version of a DVD player. Nah, no one EVER has to play a older technology in corporate America due to training or presentation
(A funny clip of a movie before a ppt)? Nah.
But, I'd like to add a warning to MSFT senior management. I know you want to force everyone to use YOUR cloud just like apple did to theirs. Wont' work. Some of us refuse to sign onto a web site and let you track all of our moves... some
distrust the cloud (Target anyone?) etc etc. All good points, now for the out of the park. The Harvard Business Review some years ago did a study on long term profitability of a company (you have to have a profit to stay in business). The
most highly correlated factor: Customer Sat. Sorry, but I don't see customer sat in all of these entries.
IF you made your product easier to use and NOT have to have a IT support person to move from a small workgroup to a server configuration (and PS, what in the heck to you get from a workgroup? File Replication, Remote access to outlook files as one
does via exchange? Really, every computer is in a workgoup any more, so there is ZERO value add in a workgroup on a MSFDT platform, however there is great value, even with a couple of users, in an Exchange/Windows Server Platform -- so why so you make
it so damned hard to implement one... Difficult for one to implement in an SMB environment (so lets just kill SBS) but growth from small business is where your growth is... just like IBM did before you, MSFT only appears to be listening to Fortune 500 it execs,
but I really digressed) This is just one more pain in the butt to use MSFT in the small environment. So what is the rational business decision? Yes one can pick MSFT but with Zero value add in the workgroup, why not them other guys (who may
be apple, or android or even some Linux platforms)
SO you want to continue to mil the cash cow, listen to your forums.
One more note on the STORE. Lets say you do pick a competitive product in the windows store. Have them been verified they don't contain malware like MSFT products? I believe the answer here is "NO" So this adds another layer of complexity
and security risk on the corporate problem of "How do I play a DVD on my laptop" I am sure none of you has ever played a movie on your laptop flying for business?
So, MSFT management, let me paraphrase the posts above: "WHY don't you support our business needs"
And remember, people buy to have their needs met..... (IBM Planned Sales Call)
If you don't meet small business needs, someone will... and that too is fraught with risk.
(For example of how to make computers easy to use in SMB I reference SBS, the Systems Management Interface tool in IBM Unix, or best of all, the AS/400.... something even Ellison couldn't kill, though he tried.

Schedule Task - Windows 2008 R2 - User Session

I am migratiing the schedule task from windows 2003 to windows 2008 and find some of behaviour change on handling user session by Task Scheduler.
I have a simple batch to call "net use" command to map a network drive for copying file to remote server. And I have scheduled 3 similar tasks and run as same user (e.g. testuser)
In windows 2003 enviornment, the mapped network drive resource will not be accessed by another schedule task. In windows 2008 R2, howerver, the network drive mapped in one of schedule task can be reached by another task. Does anyone have
idea on this behaviour change?
Here are the testing script
Test Script 1
NET USE >> D:\TEST1.LOG
NET USE Z: \\127.0.0.1\Share /PERSISTENT:NO >> D:\TEST1.LOG
ping 127.0.0.1 -n 100
NET USE Z: /DELETE
Test Script 2
NET USE >> D:\TEST2.LOG
NET USE Z: \\127.0.0.1\Share /PERSISTENT:NO >> D:\TEST1.LOG
ping 127.0.0.1 -n 100
NET USE Z: /DELETE
Test Script 3
NET USE >> D:\TEST3.LOG
NET USE Z: \\127.0.0.1\Share /PERSISTENT:NO >> D:\TEST3.LOG
ping 127.0.0.1 -n 100
NET USE Z: /DELETE
Output in Windows 2003
Test1.LOG
New connections will not be remembered.
There are no entries in the list.
The command completed successfully.
z: was deleted successfully.
Test2.LOG
New connections will not be remembered.
There are no entries in the list.
The command completed successfully.
z: was deleted successfully.
Test3.LOG
New connections will not be remembered.
There are no entries in the list.
The command completed successfully.
z: was deleted successfully.
Output in Windows 2008
Test1.LOG
New connections will not be remembered.
There are no entries in the list.
The command completed successfully.
z: was deleted successfully.
Test2.LOG
New connections will not be remembered.
Status       Local     Remote                    Network
OK           Z:
\\127.0.0.1\Share          Microsoft Windows Network
The command completed successfully.
System error 85 has occurred.
The local device name is already in use.
The network connection could not be found.
More help is available by typing NET HELPMSG 2250.
Test3.LOG
New connections will not be remembered.
Status       Local     Remote                    Network
OK           Z:
\\127.0.0.1\Share          Microsoft Windows Network
The command completed successfully.
System error 85 has occurred.
The local device name is already in use.
The network connection could not be found.
More help is available by typing NET HELPMSG 2250.

Sorry for confusing, I have udpated the script for this testing
=====================================================
Script for Schedule Task 1 - to map a network drive and issue a ping command to "sleep"
Echo %date% %time% list drive on schedule task 1
NET USE
Echo %date% %time% map drive on schedule task 1
NET USE Z: \\127.0.0.1\Share /PERSISTENT:NO
ping 127.0.0.1 -n 100 > NUL
Echo %date% %time% remove drive on schedule task 1
NET USE Z: /DELETE
Script for Schedule Task 2 - to list out any network drive are mapped.
Echo %date% %time% list drive on schedule task 2
NET USE
========================================================================
The schedule task 2 are triggered while the schedule task 1 are running, In the windows 2003, the schedule task 2 could not list out any mapped drive. In the windows 2008, however, the schedule task 2
can list the network drive mapped by schedule task 1. The question is if there are any changes between windows 2003 and 2008, hope it can clarify.
Ouput on windows 2003
Schedule task1
D:\>Echo Wed 02/06/2013 18:31:52.93 list drive on schedule task 1
Wed 02/06/2013 18:31:52.93 list drive on schedule task 1
D:\>NET USE
New connections will not be remembered.
There are no entries in the list.
D:\>Echo Wed 02/06/2013 18:31:52.98 map drive on schedule task 1
Wed 02/06/2013 18:31:52.98 map drive on schedule task 1
D:\>NET USE Z: \\127.0.0.1\Share /PERSISTENT:NO
The command completed successfully.
D:\>ping 127.0.0.1 -n 100 1>NUL
D:\>Echo Wed 02/06/2013 18:33:32.07 remove drive on schedule task 1
Wed 02/06/2013 18:33:32.07 remove drive on schedule task 1
D:\>NET USE Z: /DELETE
Z: was deleted successfully.
Schedule Task 2
d:\>Echo Wed 02/06/2013 18:32:22.54 list drive on schedule task 2
Wed 02/06/2013 18:32:22.54 list drive on schedule task 2
d:\>NET USE
New connections will not be remembered.
There are no entries in the list.
Output on windows 2008
Schedule task1
C:\Windows\system32>Echo Wed 02/06/2013 18:17:52.13 list drive on schedule task 1
Wed 02/06/2013 18:17:52.13 list drive on schedule task 1
C:\Windows\system32>NET USE
New connections will not be remembered.
There are no entries in the list.
C:\Windows\system32>Echo Wed 02/06/2013 18:17:52.16 map drive on schedule task 1
Wed 02/06/2013 18:17:52.16 map drive on schedule task 1
C:\Windows\system32>NET USE Z: \\127.0.0.1\Share /PERSISTENT:NO
The command completed successfully.
C:\Windows\system32>ping 127.0.0.1 -n 100
1>NUL
C:\Windows\system32>Echo Wed 02/06/2013 18:19:32.59 remove drive on schedule task 1
Wed 02/06/2013 18:19:32.59 remove drive on schedule task 1
C:\Windows\system32>NET USE Z: /DELETE
Z: was deleted successfully.
Schedule task2
C:\Windows\system32>Echo Wed 02/06/2013 18:18:07.69 list drive on schedule task 2
Wed 02/06/2013 18:18:07.69 list drive on schedule task 2
C:\Windows\system32>NET USE
New connections will not be remembered.
Status       Local     Remote                    Network
OK           Z:        \\127.0.0.1\Share
Microsoft Windows Network
The command completed successfully.

Oracle APEX and Windows 2008 64 Bit

Hi
We are using Oracle APEX 3.1 version and Oracle 10G HTTP Server is running on a system which is Windows 2003 32 Bit.
We are planning server Virtualization and for that i would like to know whether Oracle APEX 3.1 version is compatible with Windows 2008 64 Bit or not?
Any kind of help is appreciated.
Thanks,
Lakshmi

Hi,
Thanks for your reply.
Actually my question supposed to be whether Oracle 10G http server that we are using for APEX 3.1 version is compatible with Windows 2008 64 Bit?
If we change to Windows 2008 64 Bit do i need to install Oracle 11g http server?
Advance thanks for your help.
Lakshmi

Migrating windows 2003 standard edition to windows 2008 enterprise edition

Hi
We are using ECC 5.0 and our PRD system is running on windows 2003 standard edition,and recently we have got some physical memory problem.as windows 2003 standard edition supports only 4 GB of RAM. and we want to extend our RAM for that we are planning to upgrade os to windows 2008 enterprise edition,is that possible.and after upgrading OS what are the activities that need to be performed for SAP to run succesfully,kindly suggest.
Regards
Pranav

Hi Markus
I read note SAP Note 690432 - Windows 2003 Support in it regarding upgradation of os windows 2003 standard edition to windows 2003 enterprise edition.
Upgrade of Your Operating System
If you upgrade an existing SAP system to Windows Server 2003 perform the
following actions:
o Install the latest R3DLLINS
You find the latest dynamic link libraries R3DLLINS for Windows
Server 2003 on the EXT-Kernel CD in the NTPATCH directory.
o Replace the R/3 kernel with the EXT-Kernel.
If you do not replace it you will get error "SICK" after the first
logon attempt after the start.
In this case, download the disp+work package(s) from the SAP
Service Marketplace at service.sap.com/patches and unpack the
patch(es) to directory usr\sap\exe:
dw*_<patch-level>
Use at least patch level 186.
o Use the latest saposcol version.
This version supports the changed performance counter of Windows
Server 2003 to determine values for ST06 and RZ20.
You can find the latest version in file saposcol_<Patch Level>.CAR.
in the SAP Service Marketplace.
o SAP DB only: See SAP Note 315237.o Compatibility of the Hardware with Windows Server 2003
You can perform the upgrade to Windows Server 2003 only if the
hardware has been explicitly released for this purpose. To check,
do one of the following:
- If the Windows Server 2003 CD is available, check compatibility
with WINNT32.EXE in the \I386 directory. The exact statement
is: <DRIVE:>\I386\WINNT32 /CHECKUPGRADEONLY. The result is
stored as text file WINNT32.LOC in the present Windows
directory (e.g. C:\WINNT).
- The hardware has successfully passed SAP hardware certification
(http://www.addon.de).
- The hardware is contained in the Microsoft Hardware
Compatibility List (http://www.microsoft.com/hcl).
- The hardware has been released for Windows Server 2003 by the
manufacturer. This information is published on the
corresponding website.
o Kerberos Single Sign-On
When the SAP system is installed on Windows Server 2003 you can
setup the Kerberos Single Sign-On. If you use the kerberos protocol
the information exchanged between the SAP frontend and the
application server for authentication is encrypted.
The procedure for setting up Single Sign-On is described in all
recent installation guides which you can download from the SAP
Service Marketplace at: service.sap.com/instguides.
o SAP domain under Windows Server 2003
Follow the instructions of the Windows documentation for the
migration of a Windows NT 4 domain to Windows 2003. For the SAP
environment some additional points need to be observed.
For Windows NT 4 there are two models for the SAP system domain:
- Single domain
All users and the SAP system build one single domain. This
domain can be migrated to Windows Server 2003 and exist there
as single domain.
- Additional domain
There is one domain for the users and a second domain for the
SAP system(s). For a migration to Windows Server 2003 the SAP
system domain has to be created as child domain under the user
domain. A "Top-down" procedure is to be used. The higher domain
(the user domain) must be migrated prior to the SAP child
domain. If the user and SAP domain is part of a larger domain
structure the complete domain structure for Windows Server 2003
needs to be planned in a preparing phase. Usually, the
structure created under Windows NT 4 has to be re-arranged and
consolidated.
The name space of the root domain and all sub-ordinated domains
has to be defined and the distribution of the DNS services
needs to be determined.
Note the following:
The SAP domain has to be created as child domain.
The SAP domain must not be converted into an organizational
unit (OU). OUs are not supported by R3SETUP and R3up.
in it nowhere it is mentioned about system copy so plz suggest.

OEM System Builder License Type VS PID Check

Hi,
I have a question regarding the type of license that are the OEM System Builder one. At work, I have several boxes of Windows 7 Professional OEM System Builder licenses. Basically, it is made of a plastic DVD box wrapped in a thin carton, sealed with a small
red sticker when it's new so that you don't get to take out the plastic box from the carton. Inside the box, there's a manual and the installation DVD of Windows. On the box, there's a OEM CoA sticker that can be pealed off to stick it on a computer's chassis.
In my understanding, these licenses should be OEM CoA licenses. Is that right?
To check a license type, I use this
online PIDchecker.
After checking all my OEM System Builder CoA licenses from this website, I found out that only one was
CoA, the other one being either Retail or
VL:MAK.
I precise that I work in China Mainland and it's rather hard to get genuine products as most of suppliers provide counterfeit licenses, even when ordering PC with genuine Windows OEM license from official brand retailers like Lenovo China. When I catch them
and ask to rectify the situation, they often do so by giving me a OEM System Builder box/license. Even though I know I'm not supposed to be allowed to use these types of license as an end user, I have no choice and it's better than nothing. However, when I
started to work for my current company, several OEM System Builder licenses had already been purchased and I got suspicious of the authenticity of the products, that's why I checked the PID.
So my question is: do the Retail and VL:MAK license types found from OEM System Builder licenses mean that these products are counterfeit?

Hi,
Thanks for your advise. I didn't really realize the risks of using such a website for license check but now that you pointed out, you're right.
I'll use MGADiag tool, which I already used before, but I also would liked to check the license before installing them. Is there any official MS tool similar to PID checker, that can check the license just by manually entering it?
I'm surprised about what you said: " as an end-user you are allowed to install the OS via the OEM System Builder Kit."
When I read about the licensing policy about OEM System Builder on MS official website, I remember that only OEM system builder are allowed to use this kind of kit. That would be either big brands such as Lenovo, Dell, HP or small PC retailers that have an
OEM agreement with MS to install OEM licenses on DIY PC.
OEM System Builder licenses are available to smaller companies or hobbyists/individuals (e.g. design/build-your-own).
"Tier 1" OEM's e.g. Lenovo, HP, Dell, etc, don't use OEM-SB, they use "OEM", and have special tools provided to them by MSFT for implanting product keys within firmware/BIOS.
Tier 1 OEM's sell lots and lots of products with MSFT licenses "attached".
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!)

Windows 2008 R2 DCs machine account password expiring

We've a mixed Windows 2008/2003 environment across 30 connected sites. There is a mixture of 2008/2003 DCs. We've had an issue whereby when some of the Windows 2008 R2 DC have been rebooted, they lose there trust relationship with the domain ie
we have needed to reset the Machine Account Password for the Windows 2008 R2 DC. This only happens after the reboot. Initially the problem was only occuring on one site, but now it has happened on 3 seperate sites.
Servers trying to communicate with the effected DC, are generating Kerberos Event ID 4 (KRB_AP_ERR_Modified) .
Any ideas what may be causing this issue.
Marcus.

Looks, error indicates that the secure channel between the DC's are broken.
Refer below link to fix the issue:
http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/e9c162cb-1e26-43e0-80df-73c491c22aac/
http://social.technet.microsoft.com/Forums/ar/winserverDS/thread/61841544-ac49-49cc-8db0-ecc511941c95
Also refer:
http://blogs.technet.com/b/askds/archive/2014/07/23/it-turns-out-that-weird-things-can-happen-when-you-mix-windows-server-2003-and-windows-server-2012-r2-domain-controllers.aspx
Devaraj G | Technical solution architect

How to Mount IBM Tape Drive on windows 2008 SAP Platform

Hi Expert,
What are the steps for Mount IBM Tape drive on windows 2008 SAP Platform on Sybase Database ?
After mounting IBM Tape Drive on windows 2008 SAP Platform , can i use this for Sybase Backup purpose from DBACOKPIT ?
Kindly reply me ASAP.

Dear All,
Problem Solved by below activity :-
http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc38421.1572/doc/html/san1335472614455.html?resultof=%22%64%75%6d%70%22%20%22%64%61%74%61%62%61%73%65%22%20%22%64%61%74%61%62%61%73%22%20
1> dump database pubs2 to "\\.\TAPE0"
2> go
1> load database pubs2 from \\.\TAPE0
2> go
Please review any of these SAP Notes to see if you would be able to
setup dump/load and then copy to tape as an option.
1585981 SYB: Ensuring Recoverability for Sybase ASE (has some
comments about storing to tape drive)
1588316 SYB: Configure automatic database and log backups
1611715 SYB: How to restore a Sybase ASE database server (Windows)
1618817 SYB: How to restore a Sybase ASE database server (UNIX)
1887068 - SYB: Using external backup and restore with SAP Sybase ASE
Configuration DEVDB:
1> sp_config_dump @config_name='DEVDB' ,
2> @stripe_dir = "\\.\Tape0" ,
3> @compression = '101' ,
4> @capacity = '1520000040960' ,
5> @verify = 'header'
6> go
Configuration DEVLOG:
1> sp_config_dump @config_name='DEVLOG' with init,
2> @stripe_dir = "\\.\Tape0" ,
3> @compression = '101' ,
4> @capacity = '1520000040960' ,
5> @verify = 'header'
6> go
1> dump database DEV using config = 'DEVDB' with capacity = 87000000, init
2> go
1> dump transaction DEV using config = 'DEVLOG' with capacity = 87000000, init
2> go
and
1> dump database DEV to "\\.\TAPE0" with capacity = 87000000, init
2> go
1> dump transaction DEV to "\\.\TAPE0" with capacity = 87000000, init
2> go

Licensing change OEM to KMS (Allowable?)

Hello All,
I am very new to the forum so forgive me if I am not handling this request properly. I have a seemingly simple question, but have not been able to find a definitive answer. The question is: Can I change my
current Dell OEM licensed Windows 2008R2 Standard license version to our existing KMS license for one server? Our DR solution apparently cannot work with an OEM license version. I believe I can use the SLMGR CLI, but wanted to make sure
before I made a change I couldn't back out of. Thank you for your assistance.

Hi,
You are allowed to change an OEM-licensed product to KMS client if Software Assurance (SA) is purchased within 90 days after purchasing the OEM product. It only applies to Windows 7 or Windows Server 2008 R2, though.
For more detailed information, please refer to the article below:
Taking Advantage of Volume Licensing : KMS and the Client (part 1) - Changing the Client License Type After Installation & Postponing Activation
http://tech.sportstoday.us/windows_7/taking-advantage-of-volume-licensing---kms-and-the-client-(part-1)---changing-the-client-license-type-after-installation---postponing-activation.aspx
Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Regards,
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.

Which License is good OEM, OLP or Volume Licensing for small company

Dear Admins,
Actually I am setting up a lab for a small company with 25 users. Confused which license to purchase. Vendor sent us quotation in which he mentions we have to purchase "HP Server DL-380 -G8 Intel Xeon 2.5GHZ " in order to install windows server
2008 R2 OEM Edition CD. Actually I just want to know. Can't we purchase a assembled computer/Machine and purchase Windows Server 2008 R2 OEM CD for successful implementation?. Now, My question to you is. What is this OLP and OEM. Does OLP mean
we can install Windows Server in assemebled computer or machine and OEM means only dedicate company machine is capable to install OEM edition, Just confused, Please let me know. It is just a small company with 25 users. What do you recommend. Thank you for
your support.
Best Regards,
Fahad Ahmed.

Hi Fahad,
Couple of things to remember as well
OEM licences comes with the machine probably you have seen laptops and desktop has a windows key sticker that's an OEM license. Only limitation with OEM is you can't use OEM license anywhere else then the machine you have bought it with. If an OEM license
machine dies license will die as well.
With volume license you have the freedom to move around the license. If you have only one license on one machine at one time.
Also when you buy a windows server license it comes with 5 user CALs. So that's why you have to buy 20 more.
Now if you want to know what are the CALs, so CAL is a Client Access License require for a
user/device to access windows server. For example if you have a user and he wants to access share files or printer from the server you will require a user CAL. So if 25 users will access the Server you will require 25 CALs.
Best thing to do is to speak with your account Manager from Dell or HP regarding the license side as normally they are really good in helping.
Hope this helps :)

Windows Server 2008 R2 180 Day Trial License

Hi,
I'm running the Windows 2008 R2 Trial on VMware Player. As you can see from the link below:
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=11093
...it says it's a 180 day evaluation. But further down on the page there is no trial key. All there is is a mention that it can be activated 5 times at 10 days per activation. When it pops up saying that my copy is illegal, it takes me
to a website selling Windows 7 licenses.
I've read other articles on this and there doesn't seem to be an answer as to where the trial keys are, or what process you follow to get your 180 day evaluation? Anyone have any ideas?
Cheers,
Adrian

You need to activate the product in 10 days. This 10 day activation period can be reset 5 times by using the
rearm command. Once activated, the evaluation will run for 180 days. So you can evaluate this version for 240 days.
(10 days + 5 * 10 days using rearm) + 180 days after activating = 240 days
OEM – RETAIL – Maximum 120 days
You need to activate the product in 30 days. This 30 day activation period can be reset 3 times by using the
rearm command. So you can evaluate this version for 120 days.
30 days + 3 * 30 days using rearm = 120 days
Volume License - VOLUME_KMSCLIENT – Maximum 120 Days
You need to activate the product in 30 days. This 30 day activation period can be reset 3 times by using the
rearm command. So you can evaluate this version for 120 days.
30 days + 3 * 30 days using rearm = 120 days
You can verify the license type using the Slmgr /dlv command
For more information:
http://portal.sivarajan.com/2010/10/windows-2008-r2-evaluation-period-and.html
Thanks

Windows 2008 Server License Key not working on VirtualBox

I have a validated licensed copy of Windows 2008 Server and I need to load it on a Virtual machine (I am running Oracle VirtualBox). When I had the server running on a hardware based server it worked fine. The license key activated and it worked. Now when
I load it onto the VirtualBox solution it fails. It will take it when I run the manual command but will not show my server as activated. This is for my private use only (internal home LAN) but I would prefer to have the activation be correct since I use this
setup to help keep fresh on Windows 2008 servers while being on a Linux OS with a VM software loaded. What can I do to have this server activate correctly under the VirtualBox?
Thanks,
Tom

Hi Tom,
Base on my experience, after we convert a physical computer system to virtualize environment we need to reactive it, with MAK active method we need keep this vm to connect to
internet and with KMS method please confirm this vm can communicate with your KMS server.
The related KB:
Understanding MAK Activation
https://technet.microsoft.com/en-us/library/ff793435.aspx
Volume Activation in Disconnected Environments
https://technet.microsoft.com/en-us/library/dd981010.aspx
I’m glad to be of help to you!
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]

Windows 2008 R2 OEM to Volume License change after p2v.

Similar Messages

Maybe you are looking for