Migrate from 2012 rtm to 2012 R2

I am a bit confused, if you read the migration hierarchy scenarios (http://technet.microsoft.com/en-us/library/gg682006.aspx) you can migrate from 2007 to 2012 rtm or SP1 or R2.
you can migrate from 2012 SP1/R2 to another 2012 SP1/R2
yesterday I was investigating the possibility to migrate a pilot 2012 RTM environment to a new 2012 R2 environment we just setup. as a test I was able to migrate a driverpackage, so hey: it seems to work, but why is this scenario not covered in the
technet online doc?
so: if object migration from 2012 RTM to 2012 R2 is supported, are there limitations to that scenario?

I haven't done it either but know of several cases where this has successfully been done. However, as with any migration, there are niggling issues. Unfortunately you won't be able to get any assistance with these - as you are in an "unsupported"
scenario.
I would have preferred for this to be tested properly and deemed to be "supported".
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Similar Messages

Windows server 2012: migration from 2012 standard evaluation version to 2012R2

Hello.
Is it possible то migrate
FROM: windows server 2012 standard evaluation
TO: windows server 2012R2 standard
And if it is possible then "how to"?
Activation product key for 2012 is NOT available.
Activation product key (MAK, "open licence") for 2012R2 is available.
The key for 2012R2 does not "open" 2012 evaluation version.
Thanks.

Upgrade means moving from your existing operating system release to a more recent release, while staying on the same hardware. For example, if your server is running Windows Server 2012, you can upgrade it to Windows Server 2012 R2. You
can upgrade from an evaluation version of the operating system to a retail version, from an older retail version to a newer version, or, in some cases, from a volume-licensed edition of the operating system to an ordinary retail edition.
ref : http://technet.microsoft.com/en-us/library/dn303416.aspx
Arnav Sharma | Facebook |
Twitter Please 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.

Cross Forset Migration from sccm 2012 to sccm 2012RS

Hi all,<o:p></o:p>
We have a plan to migrate
sccm 2012 to sccm 2012 R2 on trusted forest (cross forest migration)<o:p></o:p>
Please share possibility...<o:p></o:p>
Thanks, Mariappan Shanmugavel

Possibility for what?
Migration only works from ConfigMgr 2007 SP2 or from the same version of ConfigMgr 2012 thus will not be able to migrate from 2012 to 2012 R2. You will need to upgrade your 2012 site to 2012 R2 first and then perform the migration. The TechNet docs clearly
show this: http://technet.microsoft.com/en-us/library/gg699364.aspx
ANd, as Torsten pointed out, if you are simply planning on moving the existing site server, that isn't supported and won't work either.
Jason | http://blog.configmgrftw.com | @jasonsandys

Migration from Small business server 2011 standad to Windows 2012 Server Standard

Hi everyone,
I have a network with SBS 2011 standard (that is the only server) and now we are moving (migrating) to windows 2012 server standard with an exchange 2013 (not yet installed).
The main thing is that when trying to install the migration tool on the SBS server, it will not install because it is not a 2008 R2 server.
is there a workaround for this problem?
I Hope this will help. Amir Ovadia

Hi,
Would you please first let me know how did you perform the migration? Regarding the migration tool, is it the Windows Server Migration Tools in Windows Server 2012 R2? Since you need to install
the Windows Server Migration Tools on the source SBS 2011 server, I suggest we could perform the following steps to install it.
Create deployment folders for ource computers by running the
smigdeploy.exe tool (included with Windows Server Migration Tools) on your destination server.
Register Windows Server Migration Tools on source computers that are running Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, or Windows
Server 2003 by using SmigDeploy.exe.
For details, please refer to the following article.
Install, Use, and Remove Windows Server Migration Tools
http://technet.microsoft.com/library/jj134202
In addition, here are some similar threads about how to perform the migration from SBS to Windows Server 2012 Standard, maybe they are useful to us.
how to Migrate sbs 2011 to Standard 2012 server
http://social.technet.microsoft.com/Forums/en-US/e1d4b09f-8857-4ef6-9a80-6a906e76b688/how-to-migrate-sbs-2011-to-standard-2012-server
Migrate SBS 2011 to Server 2012 Standard
http://social.technet.microsoft.com/Forums/en-US/f552ef12-07a9-4f7a-bf5e-24500c3e1dc3/migrate-sbs-2011-to-server-2012-standard
Migrating from Windows SBS 2011 Essentials to Windows Server 2012 Standard
http://social.technet.microsoft.com/Forums/en-US/41d17523-c6ae-4ba6-851f-a42b16f31d2a/migrating-from-windows-sbs-2011-essentials-to-windows-server-2012-standard
As there is no specific documentation on migrating from SBS to Windows server 2012, if you want the step by step procedure about the migration, we’d better involve
SBSMigration.com for detailed information.
Thanks.
Best Regards,
Andy Qi
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Andy Qi
TechNet Community Support

Migrate from server core 2008 r2 hyper-v with failover cluster volumes to server core 2012 r2 hyper-v with failover cluster volumes on new san hardware

We are getting ready to migrate from server core 2008 r2 hyper-v with failover cluster volumes on an iscsi san to server core 2012 r2 hyper-v with failover cluster volumes on a new iscsi san.
I've been searching for a "best practices" article for this but have been coming up short. The information I have found either pertains to migrating from 2008 r2 to 2012 r2 with failover cluster volumes on the same hardware, or migrating
to different hardware without failover cluster volumes.
If there is anyone out there that has completed a similar migration, it would be great to hear any feedback you may have on your experiences.
Currently, my approach is as follows:
1. Configure new hyper-v with failover cluster volumes on new SAN with new 2012 r2 hostnodes and 2012 r2 management server
2. Turn off the virtual machines on old 2008 r2 hyper-v hostnodes
3. Stop the VMMS service on the 2008 r2 hostnodes
4. copy the virtual machine files and folders over to the new failover cluster volumes
5. Import vm's into server 2012 r2 hyper-v.
Any feedback on the opertain I have in mind would be helpful.
Thank you,
Rob

Hi Rob,
Yes , I agree with that "file copy " can achieve migration.
Also you can try "copy cluster wizard " :
https://technet.microsoft.com/en-us/library/dn530779.aspx
Best Regards,
Elton Ji
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 Subscriber Support, contact [email protected] .

Virtual Machine Manager 2012 R2 migrate from standalone to cluster - no starting

Hello,
we have migrated our Virtual Machine Manager 2012 R2 UR1 installatin from a standalone machine to a clustered version.
But now the cluster instance won't startup.
- uninstall the standalone virtual machine manager 2012 with the retain database option.
- created failover cluster
- installed vmm into cluster and pointed to existing database.
- added second node
The error we now get is out of the report.txt:
------------------- Error Report -------------------
Error report created 17.04.2014 19:38:57
CLR is not terminating
--------------- Bucketing Parameters ---------------
EventType=VMM20
P1(appName)=vmmservice.exe
P2(appVersion)=3.2.7620.0
P3(assemblyName)=ImgLibEngine.dll
P4(assemblyVer)=3.2.7620.0
P5(methodName)=Microsoft.VirtualManager.DB.Adhc.StoredCertificate.CacheVMConnectCertificate
P6(exceptionType)=System.AggregateException
P7(callstackHash)=7b6a
SCVMM Version=3.2.7620.0
SCVMM flavor=C-buddy-RTL-AMD64
Default Assembly Version=3.2.7620.0
Executable Name=vmmservice.exe
Executable Version=3.2.7510.0
Base Exception Target Site=140721289766296
Base Exception Assembly name=mscorlib.dll
Base Exception Method Name=System.Security.Cryptography.CryptographicException.ThrowCryptographicException
Exception Message=One or more errors occurred.
EIP=0x00007ffc469c43c8
Build bit-size=64
------------ exceptionObject.ToString() ------------
System.AggregateException: One or more errors occurred. ---> System.Security.Cryptography.CryptographicException: The specified network password is not correct.
at System.Security.Cryptography.CryptographicException.ThrowCryptographicException(Int32 hr)
at System.Security.Cryptography.X509Certificates.X509Utils._LoadCertFromBlob(Byte[] rawData, IntPtr password, UInt32 dwFlags, Boolean persistKeySet, SafeCertContextHandle& pCertCtx)
at System.Security.Cryptography.X509Certificates.X509Certificate.LoadCertificateFromBlob(Byte[] rawData, Object password, X509KeyStorageFlags keyStorageFlags)
at System.Security.Cryptography.X509Certificates.X509Certificate2..ctor(Byte[] rawData, SecureString password, X509KeyStorageFlags keyStorageFlags)
at Microsoft.VirtualManager.DB.Adhc.StoredCertificate.CacheVMConnectCertificate(StoredCertificate cert)
at Microsoft.VirtualManager.DB.Adhc.StoredCertificate.ImportCertificates(List`1 certificates, ReportCertImportFailure ReportImportFailure)
at Microsoft.VirtualManager.DB.Adhc.StoredCertificate.ImportAllCertificates(ReportCertImportFailure ReportImportFailure)
at Microsoft.VirtualManager.Engine.VirtualManagerService.LoadCertificates()
at Microsoft.VirtualManager.Engine.VirtualManagerService.TimeStartupMethod(String description, TimedStartupMethod methodToTime)
at System.Threading.Tasks.Task.Execute()
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at Microsoft.VirtualManager.Engine.VirtualManagerService.WaitForStartupTasks()
at Microsoft.VirtualManager.Engine.VirtualManagerService.TimeStartupMethod(String description, TimedStartupMethod methodToTime)
at Microsoft.VirtualManager.Engine.VirtualManagerService.ExecuteRealEngineStartup()
at Microsoft.VirtualManager.Engine.VirtualManagerService.TryStart(Object stateInfo)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.TimerQueueTimer.CallCallback()
at System.Threading.TimerQueueTimer.Fire()
at System.Threading.TimerQueue.FireNextTimers()
---> (Inner Exception #0) System.Security.Cryptography.CryptographicException: The specified network password is not correct.
at System.Security.Cryptography.CryptographicException.ThrowCryptographicException(Int32 hr)
at System.Security.Cryptography.X509Certificates.X509Utils._LoadCertFromBlob(Byte[] rawData, IntPtr password, UInt32 dwFlags, Boolean persistKeySet, SafeCertContextHandle& pCertCtx)
at System.Security.Cryptography.X509Certificates.X509Certificate.LoadCertificateFromBlob(Byte[] rawData, Object password, X509KeyStorageFlags keyStorageFlags)
at System.Security.Cryptography.X509Certificates.X509Certificate2..ctor(Byte[] rawData, SecureString password, X509KeyStorageFlags keyStorageFlags)
at Microsoft.VirtualManager.DB.Adhc.StoredCertificate.CacheVMConnectCertificate(StoredCertificate cert)
at Microsoft.VirtualManager.DB.Adhc.StoredCertificate.ImportCertificates(List`1 certificates, ReportCertImportFailure ReportImportFailure)
at Microsoft.VirtualManager.DB.Adhc.StoredCertificate.ImportAllCertificates(ReportCertImportFailure ReportImportFailure)
at Microsoft.VirtualManager.Engine.VirtualManagerService.LoadCertificates()
at Microsoft.VirtualManager.Engine.VirtualManagerService.TimeStartupMethod(String description, TimedStartupMethod methodToTime)
at System.Threading.Tasks.Task.Execute()<---
Maybe someone has an idea where to look at.
Best Regards,
Marcus
Marcus Lehmann

Hi,
nope, we solved it.
It seems that this behavior occurs only under special circumstances.
Scenario is:
1. RDP Gateway connection to our Hyper-V Hosts (We need it for our Windows Azure Pack installation). A certificate is needed to encrypt the connection between RDPGW and Hyper-V host. This certificate is distributed by the VMM to the Hyper-V Hosts with the
private key.
2. Migrating from standalone installation to High Availability therefore migrating from DPAPI to DKM
It looks like that the key or the password to unencrypt the private key, which is stored in the database, is itself stored in the DPAI/DKM.
So when you try to get the migrated Service online the error report in my first post is generated.
What we did was fiddeling around in the database. Make sure you have a backup !!
You need two tables:
tbl_ADHC_Host
tbl_VMM_CertificateStore
1. Go to the table "tbl_ADHC_Host" and edit the key fk_ADHC_Host_VMM_CertificateStore and set "Enfore Foreign Key Constraint" to "No".
2. get the value "VMConnectCertficateID" from the table "tbl_ADHC_Host"
3. Go to the table "tbl_VMM_CertificateStore" and delete the Certficate with the value which equals the "VMConnectCertificateID". Note: Corresponding Certificate in the CErtificatestore table should have something in the column "PrivatekeyPassword"
and an ObjectType of 6.
4. The service should now start and you can reconfigure the certificate used for the encryption between your RDPGW and Hyper-V Hosts, like you did before.
5. Go to the table "tbl_ADHC_Host" and edit the key fk_ADHC_Host_VMM_CertificateStore and set "Enfore Foreign Key Constraint" back to "Yes".
Hope that helps. ;)
Best Regards,
Marcus
Marcus Lehmann

Migrating From Window Server 2003 to Window Server 2012 for Web server deployment and Developmemt Machine is on Window Server 2008

Hi Microsoft Team,
We need your urgent advice and that is also on priority:
Issue Description: We need to migrate from
WINDOW SERVER 2003 to WINDOW SERVER 2012 while the development activity will be carried
under WINDOW SERVER 2008 as DEVELOPMENT BOX.
.NET Framework Version: 3.5 ( For both DEVLOPMENT(WINDOW SERVER 2008) and WEBSERVER(to WINDOW SERVER 2012))
IIS Version: 7.5 (For both DEVLOPMENT(WINDOW SERVER 2008) and WEBSERVER(to WINDOW SERVER 2012))
Need your quick advice Is that configuration feasible for Development and
Deployment (Web Server).
Highly appreciate your response as this will depend which product we need to buy also if you feel any showstopper or concern. Please let us know.

Hi,
As suggested by Tim, in order to get better assistance, we can ask for help in the following IIS forum.
IIS Forum
http://forums.iis.net/
In addition, regarding migrating from Windows Server 2003 to Windows Server 2012, the following blog can be referred to for more information.
Step-By-Step: Active Directory Migration from Windows Server 2003 to Windows Server 2012
http://blogs.technet.com/b/canitpro/archive/2013/05/27/step-by-step-active-directory-migration-from-windows-server-2003-to-windows-server-2012.aspx
Best regards,
Frank Shen

Active Directory Migration from 2003 to 2012 Process Flow

We are planning to migrate from Windows Server 2003 AD to Windows server 2012 Server for 6000 Users,
Can any one suggest on Following .
1)What is the Best and Safe Way to do Migration
2) What are the Precautions should take,
3) How much downtime it will take,
4) If migration Failed how we can revert to Earlier
5) How to do Migration Step by Step
Current Environment:
Domain Having One PDC(server 2003 R2) and 8 ADC(Server 2003 R2) in Different Locations
PDC having All FSMO Roles and Global Catalog
Exchange server 2007 was integrated to Active Directory
And some Application are integrated to Active Directory

1) I would recommend you first run a test of the steps in test before you do this in production. Otherwise your production becomes test.
2) By doing in test, you have taken a large amount of the risk out of the upgrade since, in test you should be able to look for any unforseen issues. The easiest way to test is to build a virtual fence from production and clone the DC's and member
servers that you want to test against (This is assuming you are running in a virtual environment). Ensure that you production environment is error free.
http://blogs.dirteam.com/blogs/paulbergson/archive/2009/01/26/troubleshooting-active-directory-issues.aspx
3) There should be no downtime at all, you can just extend the schema and then promote a new 2012 DC (I would recommend R2 if you can).
4) Before you do the schema extension you should take 2 backups on two different DC's. Taking two gives you less of a chance of a problem if one of the backups fails.
5)
Take a backup
Extend the schema
Join the 2012 R2 servers to the domain
Add the ADDS role to the 2012 R2 member servers
Promote the 2012 R2 DC's
Transfer the FSMO roles to the 2012 R2 DC's (Not required but recommended)
If you want to retire the 2003 DC's, then you will need to make sure that any clients pointing to the 2003 DC's for DNS are pointing to other DC's.
If you do retire the 2003 then you can think about updating the DFL and FFL of the domain and forest.
Paul Bergson
MVP - Directory Services
MCITP: Enterprise Administrator
MCTS, MCT, MCSE, MCSA, Security, BS CSci
2012, 2008, Vista, 2003, 2000 (Early Achiever), NT4
Twitter @pbbergs http://blogs.dirteam.com/blogs/paulbergson
Please no e-mails, any questions should be posted in the NewsGroup.
This posting is provided AS IS with no warranties, and confers no rights.

DNS EventID 4015 on PDC since Domain Migration from 2003 R2 = 2012

Hi,
following problem here:
2 Domain Controllers with AD Integrated DNS Zone, migrated from 2003 R2 to 2012. One Single Root Forest.
The Primary Domain Controller shows every 2, 3 or 4 hours the DNS EventID 4015. No further error is available: (which is may emty) "".
Only on the Details pane you can find this Information:
======================================
- System
- Provider
   [ Name] Microsoft-Windows-DNS-Server-Service
   [ Guid] {71A551F5-C893-4849-886B-B5EC8502641E}
   [ EventSourceName] DNS
- EventID 4015
   [ Qualifiers] 49152
   Version 0
   Level 2
   Task 0
   Opcode 0
   Keywords 0x80000000000000
- TimeCreated
   [ SystemTime] 2013-12-10T19:48:17.000000000Z
   EventRecordID 2456
   Correlation
- Execution
   [ ProcessID] 0
   [ ThreadID] 0
======================================
The Migration was made by the following steps:
Bring Up the first 2012 MigrationDC as 3rd DC to the Domain.
Move the FSMO Roles to the 2012 MigrationDC
DHCP Data migrated with Server Migration Tools, IAS Data with iasmigrader.exe exported
DCPromo DC1 (2003 R2) and Format C:
Install a fresh 2012 Installation on old DC1 an rename it again with the original Name DC1
DHCP Data migrated with Server Migration Tools, IAS Data with iasmigrader.exe exported
DCPromo DC2 (2003 R2) and Format C:
Install a fresh 2012 Installation on old DC2 an rename it again with the original Name DC2
Move Back the FSMO Roles to DC1
DCPromo the first 2012 MigrationDC
Metadata Cleanup for MigrationDC
DCDIAG /V /C Shows no Errors, all works good, the funny Thing is, that only DC1 Shows the DNS EventId 4015 in production evironment. The only exception is, that if you reboot DC1 (i.e. for maintenance, upates etc) than the error appears on DC2. Exactly on
that time, if DC1 is temporarily not availble and DC2 is under "load". If DC1 is back again, the Event 4015 Ends on DC2 and Comes back to DC1!!!
I backupped and restored DC1 and DC2 in an lab Environment, the funny Thing is that the EventID 4015 doesnt appear in lab Environment. The difference between prod and lab is: prod is bare metal with 2 teamed nics, lab is hyper-v vm's with 2 virtual teamed
nics. same IP's etc... DNS NIC Settings are the same.
It Looks like you can only produce the error in the production lab if you have the DC under "load".
This Event was discussed here more than one time in the Forum, but the issues doesnt match 100% to my Problem. No RODC is available in my prod Environment, the EventID 4015 has no further Errors "" in the Eventlog like in other Posts.
Ace Fekays blog :" Using ADSI Edit to resolve conflicting or duplicate AD Integrated Zones" was helpful for metadata cleanup, but it could not fix the EventId 4015 away. Because we had no Problems with disappearing zones...
Maybe Enabling NTDS Verbose Logging in the registry is helpful, but i dont know for what i have to Keep an eye out?
The thread
http://social.technet.microsoft.com/Forums/windowsserver/en-US/c0d3adb4-67d2-470c-97fc-a0a364b1f854/dns-server-error-event-id-4015-after-replacing-domain-controller-with-another-using-same-name?forum=winserverDS seems to match to my Problem, but also no
soulution available...
Any ideas what causes this "ugly" Event without noticable consequences?

Zonenname
Typ
Speicher
Eigens
chaf
ten
Cache
AD-Domain
_msdcs.our-domain-name.com
Primary
AD-Forest
Secure
0.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
1.1.10.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
1.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
1.18.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
10.10.10.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
10.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
11.10.10.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
11.18.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
11.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
11.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
11.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
11.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
128.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
13.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
13.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
13.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
13.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
130.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
15.18.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
15.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
15.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
15.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
15.29.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
15.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
16.10.10.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
16.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
16.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
17.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
17.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
17.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
17.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
17.29.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
17.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
19.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
19.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
19.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
196.169.193.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
2.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
20.10.in-addr.arpa
Primary
AD-Domain
Secure
Rev
20.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
200.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
21.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
21.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
21.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
23.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
23.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
23.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
23.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
239.24.217.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
25.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
25.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
25.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
25.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
252.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
252.22.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
252.23.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
252.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
252.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
252.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
253.18.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
253.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
253.22.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
253.23.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
253.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
253.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
253.26.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
253.29.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
253.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
254.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
254.18.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
254.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
254.22.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
254.23.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
254.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
254.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
254.29.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
254.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
255.10.10.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
27.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
27.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
27.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
29.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
29.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
3.18.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
3.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
3.22.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
3.23.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
3.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
3.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
3.26.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
3.29.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
3.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
31.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
31.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
32.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
33.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
35.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
37.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
39.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
41.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
43.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
45.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
47.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
49.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
5.18.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
5.19.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
5.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
5.22.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
5.23.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
5.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
5.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
5.29.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
5.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
50.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
51.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
52.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
53.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
54.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
55.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
60.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
62.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
64.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
7.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
7.18.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
7.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
7.22.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
7.23.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
7.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
7.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
7.29.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
7.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
70.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
80.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
88.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
9.18.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
9.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
9.22.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
9.23.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
9.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
9.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
9.29.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
9.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
our-domain-name.com
Primary
AD-Domain
Secure
Agi
ng
TrustAnchors
Primary
AD-Forest

Steps SSIS and SSAS Migration from sql server 2005 to 2012?

steps SSIS,SSRS and SSAS Migration from sql server 2005 to 2012? any precautions to take while migration.
any documentation or any specified steps.

Hi Vijay,
According to your description, you want to migrate SQL Server Integration Services and SQL Server Analysis Services from SQL Server 2005 to SQL Server 2012.
For how to migrate SQL Server Integration Services, please refer to the article:
http://www.bidn.com/blogs/DevinKnight/ssis/2718/upgrading-packages-to-ssis-2012.
In addition, since the issue regards SQL Server Integration Services. I suggest you post the question in the SQL Server Integration Services forums at
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?forum=sqlintegrationservices.
For how to migrate SQL Server Analysis Services, please refer to this article:
http://www.codeproject.com/Articles/435703/Migration-from-SQL-server-to.
In addition, since the issue regards SQL Server Analysis Services. I suggest you post the question in the SQL Server Analysis Services forums at
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?forum=sqlanalysisservices. It is appropriate and more experts will assist you.
Regards,
Michelle Li

Migrating from Marimba 8.1 to Configuration Manager 2012 R2

Good morning all,
I have been tasked with architecting a migration from Marimba 8.1 to Configuration Manager 2012 R2 and I noticed that there is almost no material available in the web about this, can someone provide whatever insight information possible?
Thanks in advanced for your help on this matter
Ed
edthefixer

Jeff,
I agree with you on some of your thoughts, I should've describe the situation better.... I am not trying to migrate anything from Marimba, I am architecting an entire ConfigMgr 2012 R2 infrastructure altogether, what I am trying to do is (because I have
to rationalize and normalize their DSL) see if I can salvage any applications and some level of their customization to convert them into ConfigMgr applications.... they have about 3000 apps and not all of them are in .msi format, Marimba uses a very strange
folder format for this.... trying to see if anyone out there has dealt with this before.
Ed
edthefixer

MDT 2012 to Migrate from Windows 2003 32 Bit to Windows 2012 R2 64 Bit

I have used MDT for so long however only for client OS upgrade - XP to Windows 7/8.
We wish to use MDT to migrate from Windows 2003 32 Bit to Windows 2012 R2 64 Bit. All servers are virtual on HyperV or VMWare - plan is to use USMT hardlink Migration.
Is this supported? Has anyone used this for server migration?
Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"

Thanks Keith for your reply.
Even is USMT does not work, we are ok. SMIGdeploy will be helpful.
Basically, want MDT to run some scripts on the Windows 2003 server, post which install Windows 2012 and join it to the existing domain with the same computer name.
Then hydration kit to help with the installation of features etc. Also, we would like to take a complete backup to a WIM before migrating.
I am sure this is workable.
Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"

Inter-site replication and KCC, when migrating from 2008 SP1 to 2012 R2

Hello,
We have a very simple AD infrastructure, two sites. I have built out a 2012 R2 server, extended the AD schema and promoted it to a domain controller. Reviewing the existing AD replication topology, we currently have a 2008 SP1 server as a DC
designated as the source/destination for inter-site replication, which appears to have been decided by KCC.
I will be decomming this 2008 SP1 server, having migrated off the FSMO roles to a few other DCs.
Will KCC automatically know to adjust the replication topology when the 2008 SP1 DC is offline? Should I demote it after migrating off the FSMO roles?
Thanks,
Matt

Hi,
Thanks for your post.
By default, the KCC reviews and makes modifications to the Active Directory replication topology every 15 minutes to ensure propagation of data, either directly or transitively, by creating and deleting connection objects as needed. The KCC recognizes
changes that occur in the environment and ensures that domain controllers are not orphaned in the replication topology.
For more detail information, you could refer to:
http://technet.microsoft.com/en-us/library/cc961781.aspx
For the migration, you could transfer the Flexible Single Master Operations (FSMO) Role and remove the Windows 2008 R2 domain controller, please refer to:
Step-By-Step: Active Directory Migration from Windows Server 2008 R2 to Windows Server 2012 R2
http://blogs.technet.com/b/canitpro/archive/2014/05/28/step-by-step-active-directory-migration-from-windows-server-2008-r2-to-windows-server-2012.aspx
Regards.
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]

DFS New Setup migrating from 2003 R2 file server to 2012 Server STD

We currently have a 2003 R2 flat file server with multiple layers of nested network shares with over 2.5TB of data. We want to migrate to DFS on 2012 Server standard version with deduplication enabled. We have never worked with DFS and deduplication and
any white paper on DFS and deduplication would be greatly appreciated. Not finding anything on DFS step by step for 2012 and in particular migrating from 2003 file share to 2012 server DFS.

Thank you for the URL to your DFS write up. This was very helpful in my research of DFS. I have a couple of questions. Do I have to start DFS with two servers? I completely understand why you should have more than one server in the DFS pool (high
availability) but is it necessary? Also after setting up the two 2012 Servers with DFS, namespaces, and new shares managed by DFS manager, how do we migrate (move or copy) the existing shares to new server without losing the permissions? From what I've read
in your write-up all end users with have read and write permissions and admins have full. Also is there a best practice on how nested the shares should be setup within DFS? From looking at your write up the shares are one folder deep only. At this
company I'm migrating from a file server with shares 3-8 layers deep build up over the last 20 years.

Migrating from DHCP 2003 to DHCP 2012

Hi,
i'm planning to migrate from DHCP 2003 to DHCP 2012 or DHCP 2012 R2 failover.
Saw those instructions:
extract the configuration in .TXT
netsh dhcp server export c:\temp\dhcp.txt all
copy this file on your server 2012 in temp or elsewhere
import the configuration with this command
netsh dhcp server import c:\temp\dhcp.txt all
if you have the error "TLS supported but not configured"
remove all the option in "Server Option" like 003 Router 006 DNS SERVERS and put it back after doing the import
now i have some questions:
1. is it recommended to build 2 2012 DHCP configured as failover on virtual machines ? (hyper-V)
2. do those dhcp servers have to or recommended to be DNS also or can they be only DHCP servers ?
3. my AD functionality level is 2003 - is it a problem for this migration ?
4. virtual or physical ? whats is recommended ?
5. any other considerations ?
TNX

Hi,
Virtual or physical will both work. It doesn't matter, as long as the two servers can communicate with each other.
You do not need DNS installed on the same server, but you can install it without hurting anything.
I believe that the AD level has no effect because you can have DHCP failover even on workgroup computers.
-Greg
http://technet.microsoft.com/en-us/library/dn338983.aspx#specs

Migrate from 2012 rtm to 2012 R2

Similar Messages

Maybe you are looking for