Migrating PDC role from SBS 2008 to Server 2012

Greetings everyone
Are there any special considerations or steps that need be done when elevating my BDC running Server 2012 from a PDC running SBS 2008? We are wanting to remove the SBS machine entirely as we no longer need it and could possibly be of use to one of our clients
down the road.
Thank You
Additional Info: We have already migrated Exchange to the cloud and is no longer hosted on our SBS server. The only function the SBS server has at the moment is being the PDC.

If you haven't seen it already you'll probably want to check out
http://blogs.technet.com/b/infratalks/archive/2012/09/07/transition-from-small-business-server-to-standard-windows-server.aspx which describes the entire process, though obviously in your case you don't need to worry about the Exchnage side of things.
The main thing in your case will moving the FSMO roles over to the new server so the old SBS box is no longer required. There's a link to the process in that blog post, though as I understand it when 2012 is the destination the recommended route is to grab
the roles from 2012 rather than give them up from 2008. There's a good step by step guide to the process here
http://www.waronerrors.com/kb/how-to-transfer-fsmo-roles-from-windows-server-2003--2008-to-windows-server-2012.aspx though obviously the main thing to note is that as soon as you move the FSMO roles you have 21 days in which to complete the migration. After
that time the SBS box will automatically restart periodically (I think after an hour from memory).

Similar Messages

SBS 2008 to Server 2012 R2 Active Directory Migration

Is there a tool that i can use to migrate Active Directory from SBS 2008 to Server 2012 R2?

There is no special tool for your situation. While there is a tool called ADMT that you may see mentioned if you search enough, it isn't really well suited for what you want.
With that said, there is also no *need* for a tool as I've already said. Nor do you need to recreate the users and have mismatched SIDs. You will add the 2012 machine to your existing domain and make it a domain controller. Yes, that means you will have
two DCs (for a time.) This is how larger organizations handle multiple DCs all the time, and they obviously don't go and create the same user on each DC. That is where the domain replication comes in. Your new server will be a DC and will replicate
all of the users *and* SIDs from the existing SBS server.
Then, when you are ready, you decommission the SBS 2008 server gracefully and the new 2012 server becomes your sole DC, but has AD completely intact. It is a tried and true practice, both within and outside of the SBS world, and has been done many many times.

Migrate SBS 2008 to Server 2012 R2 Std

Thank you for your reply. The Setup is a 2012 HV with three VM's = DC, Exchange and Terminal Server. The Exchange will be 2010. It was decided to stay with Emails on the Server by the company director, we don't require office 365
I think the migration of 2008 to 2012 dc should be fine, but it was migrating the exchange 2007 to exchange 2010 that I was not sure about, my notes I have were actually for 2003 sbs's that were going to use office 365 so that's why I was enquiring after the email migration
thanks

Hello
We have a SBS 2008 Server that is going to be migrated to Server 2012 R2. The 2012 has two virtual machines - one for the new Domain and the other is for email exchange. We have instructions for migrating a SBS 2003 Server to 2012 Server that we were told was successful - can I apply these same steps to a SBS 2008 Server? IT involves promotion 2012 to DC, migrating AD (FSMO, scheme master global catalog) and migrate dhcp.
for the emails, is there a MS guide to migrating SBS 2008 mailboxes to the 2012 R2 email server?
Thanks
This topic first appeared in the Spiceworks Community

Migrating Small Business Server 2008 to Server 2012 R2 Standard

Hi All,
We are going to migrate SBS 2008 to Server 2012 R2 Standard for one of our customer.
We cannot find a proper guide to do the migration. Any idea for this process.
We already migrated email to Office 365. We are going to migrate Active Directory and Shared data to new Server 2012 R2 Standard.
Thanks,
MKH

Hi,
Thanks for your posting.
There is a similar thread has been discussed:
Migrating from SBS 2008 to Windows Server 2012 R2 (NOT Essentials and with NO Exchange)
http://social.technet.microsoft.com/Forums/en-US/1276d2d3-a8f2-4786-82f3-4308a2affb11/migrating-from-sbs-2008-to-windows-server-2012-r2-not-essentials-and-with-no-exchange?forum=smallbusinessserver
Regards.
Vivian Wang

Migrate Application Role from uat to prod in 11.1.1.6.10

Hi All,
We have to migrate the UAT Application Roles to Prod instance. I followed Rittman Mead policy store migration. servers in LINUX
http://www.rittmanmead.com/2011/04/oracle-bi-ee-11g-migrating-security-policy-store-part-2/
But at MigrateSecurityStore step, I am facing an issue with the wlst script which is throwing below error.
I am getting bellow error
wls:/offline> migrateSecurityStore(type="appPolicies",srcApp="obi",configFile="/ usr/app/MW/SecurityMigration/jps-config-policy.xml",src="sourceFileStore",dst="t                                                                                                         argetFileStore",overWrite="false")
Oct 17, 2013 11:41:27 AM oracle.security.jps.internal.config.xml.XmlConfigurationFactory initDefaultConfiguration
SEVERE: org.xml.sax.SAXParseException: The XML declaration must end with "?>".
Command FAILED, Reason: The XML declaration must end with "?>".
Traceback (innermost last):
File "<console>", line 1, in ?
File "/usr/app/MW/oracle_common/common/wlst/jpsWlstCmd.py", line 955, in migrateSecurityStore
File "/usr/app/MW/oracle_common/common/wlst/jpsWlstCmd.py", line 927, in migrateSecurityStoreImpl
        at oracle.security.jps.internal.tools.utility.source.JpsInitializerSource.getSources(JpsInitializerSource.java:155)
        at oracle.security.jps.internal.tools.utility.JpsUtility.<init>(JpsUtilty.java:62)
        at oracle.security.jps.internal.tools.utility.JpsUtilMigrationPolicyImpl.migrateAppPolicyData(JpsUtilMigrationPolicyImpl.java:151)
        at oracle.security.jps.tools.utility.JpsUtilMigrationTool.executeCommand(JpsUtilMigrationTool.java:231)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
oracle.security.jps.JpsException: oracle.security.jps.JpsException: The XML declaration must end with "?>".
This is config.xml file
<?xml version='1.0' encoding='utf-8'? standalone='yes'?>
<jpsConfig xmlns="http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd">
   <property name="oracle.security.jps.jaas.mode" value="Off"/>
   <propertySets>
<propertySet name="sam1.trusted.issuers.1">
<property name="name" value="www.oracle.com" />
</propertySet>
</propertySets>
   <serviceProviders>
      <serviceProvider type="POLICY_STORE" name="policystore.xml.provider" class="oracle.security.jps.internal.policystore.xml.XmlPolicyStoreProvider">
         <description>XML-based PolicyStore Provider</description>
      </serviceProvider>
   </serviceProviders>
   <serviceInstance name="srcpolicystore.xml" provider="policystore.xml.provider" location="/usr/app/MW/SecurityMigration/uat/system-jazn-data.xml">
<description>File Based Policy Store Service Instance</description>
</serviceInstance>
<serviceInstance name="policystore.xml" provider="policystore.xml.provider" location="/usr/app/MW/SecurityMigration/prod/system-jazn-data.xml">
<description>File Based Policy Store Service Instance</description>
</serviceInstance>
   </serviceInstances>
    <jpsContexts default="default">

<jpsContext name="sourceFileStore">
<serviceInstanceRef ref="srcpolicystore.xml"/>
</jpsContext> <jpsContext name="targetFileStore">
<serviceInstanceRef ref="policystore.xml"/>
</jpsContext>
</jpsContexts>
</jpsConfig>
Please let me know if i need to provide further inputs.Appreciate your help.

make sure you are running the wlst.sh from this path /MWHOME/Oracle_BI1/common/bin/wlst.sh
you can take a look at this too Migrating Security Policies from Development to Standalone WLS 11g
http://ssssupport.blogspot.com/2013/02/obiee-11g-application-role-migration.html
Obiee11g: Migrating application role from DEV to Prod server in obiee11g

Migrating Data from MySQL to SQL Server 2012

Hi all,
I'm Migrating a database from MySQL to SQL Server 2012, using SSMA for MySQL v5.2.1258. I've got the schema migrated over and have resolved any migration issues (stored procedures / views), but when it comes to migrating over the data I'm just hitting
a wall.
None of the data is migrating and when the migration report is displayed every table has a red x against it's Status. The Output box has the following:
Data migration operation has finished.
0 table(s) successfully migrated.
0 table(s) partially migrated.
64 table(s) failed to migrate.
I've seen on the forum that someone else was having the same problem
(http://social.msdn.microsoft.com/Forums/en-US/sqlservermigration/thread/b835f4b3-3d93-42a4-9b6b-d21d3dfd8dab/)
I've set the project settings mode to default, still getting the same error and tried using both Client Side Data Migration and Server Side migration, with both giving the same result. I've tried going through the step-by-step blog as well.
I am doing something really stupid? There are 64 tables, so don't really want to try doing exports from each table and importing it into the new database.
Hope someone can help.
Cheers
Alex

Hello,
I don’t have suggestions for you, but you can try contacting the SQL Server Migration Assistant (SSMA) Team via e-mail ([email protected])
to see if they can provide a solution on this scenario.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Removing Exchange 2007 from SBS 2008 (In an Exchange 2010 Coexistance Scenario) - In order to remove 2007 Mailbox Objects from Active Directory and remove the SBS2008 server completely

I'm trying to remove Exchange 2007 from an SBS 2008 server
(Server 2008 Standard FE). My ultimate goal is to completely remove the SBS 2008 Server from the network environment.
We have an Exchange 2010 Coexistence Scenario and Mailboxes/Public Folders/etc have been moved over to the 2010 mail server, on Server 2008 R2.
I have moved all Shares, FSMO roles, DHCP, DNS, etc over to their respective servers. We have two full blown DC's in the environment.
I'm ready to remove Exchange 2007 from SBS 2008 and DCPROMO the server. I can NOT seem to find a TechNet article that shows me how
to proceed in this kind of scenario. I am trying to use the TechNet article:
http://technet.microsoft.com/en-us/library/dd728003(v=ws.10).aspx
This article references Disabling Mailboxes, Removing OAB, Removing Public Folder Databases, then uninstalling Exchange using the Setup Wizard.
When I go to Disable Mailboxes I get the following error:
Microsoft Exchange Error
Action 'Disable' could not be performed on object 'Username (edited)'.
Username (edited)
Failed
Error:
Object cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.
OK
I really don't see why I need to Disable Mailboxes, Remove OAB and Public Folder Databases since they have been moved to 2010. I just want
to remove Exchange 2007 and DCPROMO this server (actually I just want to remove any lingering Exchange AD Objects referring to the SBS 2008 Server, using the easiest and cleanest method possible).
Can someone point me in the right direction?
Thanks!

Hi,
Based on your description, it seems that you are in a migration process (migrate SBS 2008 to Windows Server
2008 R2). Now, you want to remove Exchange Server and demote server. If anything I misunderstand, please don’t hesitate to let me know.
On current situation, please refer to following articles and check if can help you.
Transition
from Small Business Server to Standard Windows Server
Removing SBS 2008 –
Step 1: Exchange 2007
Removing SBS 2008 – Step 2:
ADCS
Removing
SBS 2008 – Step 3: remove from domain / DCPROMO
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft
does not guarantee the accuracy of this information.
Hope this helps.
Best regards,
Justin Gu

Upgrading from SBS 2008 and Exchange Server 2007 and Adding Modest Failover Protection

I haven't seen anyone describe this scenario, so maybe it can't be done, but it seems it should work. Can someone either confirm this is viable or set me straight and tell me it's not wise (and if not, why not).
I currently have SBS 2008 (2008 Server + Exchange Server 2007 + some other components). I use redirected folders so all my user data is stored primarily on the server, and then sync'd with their local harddrives for roaming use and as an additional
backup precaution. I want to upgrade to a modern version of Exchange (don't care too much about the underlying server OS, but seems like a good time to upgrade everything). I also want to improve the reliability for rapid recovery in the event of a system
failure. I have always felt nervous with SBS because it only runs on a single server.
My plan is:
Install Windows Server 2012 Standard on a new server machine
Join that new server to the existing SBS domain and sync the users, etc.
Install Exchange Server 2013 on the new 2012 Server
Migrate the existing Exchange data and account info to the new server
Demote the SBS Server and promote the new server to primary DC
Reformat the old SBS server and install Windows Server 2012 on it too, and join it to the domain as a second DC
Set up DFS Replication and keep all my user data folders between the two servers (so if one server fails, the other can take over, just not automatically like with a cluster)
Install Exchange Server 2013 on the reformatted 2012 Server box (so second instance on the domain) and set it up to sync with the first Exchange Server 2013 via DAG (so if either computer crashes, the other can take over for both Exchange Server and file
services)
Wouldn't that give me a complete slow-response failover system without the need for setting up a cluster (I know a cluster would provide instant failover protection, but I don't need that kind of speed - a manual switchover in the rare event of a server
failure is acceptable for us)? I could do this using cheap hardware for each server, because unless both servers fail at the same time, clients can point to the other server. And because it's not a formal cluster, I don't need to buy anything for a shared
SAN. This seems like such an obvious more cost-effective solution for a small network, I don't understand why this isn't a common approach, which makes me wonder if there is some reason it won't work.
Any suggestions or feedback? Are Redirected Folders still recommended for users on a Server 2012-based domain?
Thanks,
Colin
Colin

Ed, thanks again for your help. OK, so here's my updated plan (I realize I should probably check on some of these pieces on the Server group, instead of this Exchange group).
Constraints/objectives:
None of the machines are truly server grade hardware, but only 5 people on the network, so performance is generally not an issue, unless a given server is just pegged on CPU or HD due to its own internal maintenance tasks and can't respond to user requests.
Haven't seen any problems, since upgrading server from 4GB RAM to 8GB a few years ago.
Not going to buy any new hardware at this time, but do have several unused consumer-grade computers I can deploy as wimpy or moderate servers.
Main issue is to limit repair time in the event of a system failure (instant failover is not required, but want to be able to restore network functions within less than 24 hours in the event of a hardware failure) and minimize time spent on IT
maintenance.
Because of light IT maintenance (not anyone's primary job and we're too small to justify a dedicated IT person or to pay for outside help), almost every touch takes me research and time to re-learn what I haven't done in weeks, months, or years -- so also
want to keep all IT tasks as simple as possible.
We philosophically want to invest now for the next 5 years and avoid ongoing cloud fees (so zero interest in Windows Server Essentials with Exchange Online)
A little nervous about using VM's, just because I never have before, but I do respect that's probably the right way to do many of these things...
Currently I have SBS 2008 (Windows Server 2008 R2, Exchange Server 2007, WSUS 3, all with latest SP's, also includes SharePoint and other stuff, but I don't really care about most of it) on a single 8GB consumer grade system, which functions as a file
server and Exchange server. We use Redirected Folders and Offline files for all users, which works great for us and provides additional file redundancy (if server goes down, all of each user's files are also on their own machine and they can even continue
to work just fine w/o the server, losing only ability to send and receive e-mail). It has been sufficient, but I want to upgrade our version of Exchange and I am nervous that if that current one server fails, it would take me a long time to restore everything
from backup, easily many days, especially if I need to buy any replacement hardware. It is RAID1, so a single drive failure is easy to handle, but that's the only hardware redundancy for the current server.
New Plan:
Install Windows Server 2012 R2 Standard on a new modest machine (16GBR RAM, Core i7, 1TB RAID1 (may upgrade to 3 or 4 TB), 256 GB SSD boot drive, this had been my old personal computer)
Join that new server to the existing SBS domain (2008 R2/Exchange 2007), make it a DC, sync the users, etc.
Install Windows Server 2012 R2 Standard on a wimpy computer (4GB RAM Core i3 processor), leave it as a member server
Install Exchange Server 2013 on the wimpy new 2012 R2 Server (and nothing else, this will be dedicated to Exchange to make the most of such a wimpy machine)
Migrate the existing Exchange data from the old SBS Exchange 2007 server and account info to the new server
(or should I just create new accounts and copy the data from the user end through Outlook -- is that safer and cleaner than attempting any kind of server-level Exchange data migration?)
Demote the old SBS Server and promote the new 16GB server to primary DC. Now it's OK to take the old SBS server off the network.
Reformat the old SBS server and install Windows Server 2012 R2 on it too, and join it to the domain as a second DC (and possibly DCPROMO it to be the main server)
Install Exchange Server 2013 in a VM on the reformatted 2012 R2 Server box (so second instance on the domain for Exchange redundancy) and set it up to sync with the first Exchange Server 2013 via DAG OR set up another physical wimpy member server and install
it there. In any case, do NOT install Exchange directly on either DC.
Set up DFS Replication or a Failover Cluster (still need to research this, but I had planned on DFS, thinking Cluster required shared drive, but Ed corrected me on this) between the two DC's for redirected files and keep all my user data folders between
the two servers. We don't need automatic failover, like with a cluster, a manual switch would be acceptable, but if no additional cost or risk to clustering the two DC's, then the auto-failover protection that provides would be better than DFS.
I think this incorporates all of your points, Ed. Does this sound right now? What's your advice on #5 (how to best migrate user data)?
Thanks so much for all your help,
Colin

How can i Migrate a database from DB2 to SQL Server 2008r2.

Hi Gurus,
Kindly help me letting me know the process for migrating the database from DB2 to SQL Server.
1) Is there any way to migrate a database from DB2 to SqlServer. (My assumption is we can not migrate database, if wrong correct me gurus).
2) Or we can only transfer data from that DB2 database to SQL Server (Using SSIS packages).
Please help me knowing the process to migrate the data from DB2 server to MSSQL server. Even am reading the documents available in the web.
Thanks in advance.. :)

Microsoft provide a migration assistant for DB2 to SQL Server:
http://www.microsoft.com/en-us/download/details.aspx?id=45296
SQL Server Migration Assistant (SSMA) is a free supported tool from Microsoft that simplifies database migration process from DB2 to SQL Server and Azure SQL DB. SSMA automates all aspects of migration including migration assessment analysis, schema and
SQL statement conversion and data migration.
Hope that helps

Migrating SAP products from a non-SQL Server platform to a SQL Server 2005

Hi,
I have another question too.
Can someone pls provide me the Considerations for Migrating SAP products from a non-SQL Server platform to a SQL Server 2005 platform?
More specifically from Oracle to SQL 2005.
Regards
Abhi

Hello
You need to perform an OSDB migration.
This will involve exporting your SAP system into a DB neutral format and then reloading this into an SQL 2005 SAP system.
Please review http://service.sap.com/osdbmigration
I recommend you review the homo/heterogeneous system copy guide for your SAP release.
Thanks
N.P.C

Is Distributed Transaction Coordinator services of the application role are required by SQL Server 2012 for clustering and support of SharePoint 2013.

All I want to know is if Distributed Transaction Coordinator services of the application role are required by SQL Server 2012 for clustering and support of SharePoint 2013.
I have been planning and deploying my companies first Windows Server 2012/SQL Server 2012 Always On cluster and Always On Availability Groups Multi-Subnet cluster and instances for SharePoint 2013, and I will be brutally honest, the documentation on either
the MSDN and TechNet leave alot to be desired. Continually finding links in the documentation will take me from a Windows 2012 reference to a page talking about Windows Server 2008 or R2, The differences of which there are so many when it comes to configurations,
settings, roles, services when working with SQL Server 2012. I have been confused, frustrated, screaming mad, with all the misdirection in this documentation. The documentation takes me windows 2008 R2 which is different than 2012!
Tired and trying to pick myself up off the floor!
Greg
Gman

In general, DTC is not required for SQL 2012. But, since you are asking specifically about SharePoint, it would be better to ask in a SharePoint forum. They would be more likely to know those situations where FTC might be needed by SharePoint.
.:|:.:|:. tim

Difference between SQL SERVER 2008 & SQL SERVER 2012 & SQL SERVER 2014

Difference between SQL SERVER 2008 & SQL SERVER 2012 & SQL SERVER 2014 ?

What sort of databases do you have OLTP? Data warehouse? What requirements do you have for High Availability?
The main features for SQL 2012/2014, as I see it:
o Support for window functions, which makes it possible to write fast queries for running totals, sliding windows etc.
o Columnstore indexes, which can speed up your data warehouse enormously. But of no interest for OLTP. Only writable in SQL 2014.
o AlwaysOn and Availability Groups, a vastly improve story for high availability and disaster recovery.
o try_convert/try_cast, you can now easily filter out values from a column which does not convert to a number. A small but essential feature.
o In memory-OLTP, a new in-memory engine in SQL 2014. This far with very limited feature set, and quite specialised.
Of the points above, the second and third require Enterprise Edition, the first and fourth are in all editions. For the last, I don't think Microsoft has announced anything yet.
There are also new stuff in the BI area, but that's out of my league.
And, oh, there is a new licensing model - which I think is holding more than one customer back.
Erland Sommarskog, SQL Server MVP, [email protected]

Copy Templates from VMM 2008 to VMM 2012 R2

Hi,
I would like to know if it was possible to copy Templates from VMM 2008 to VMM 2012 R2 ?
Thank you

I have never tried this, but you can for sure re-use the physical objects like VHD's, ISO's etc.
The template configuration and profiles are metadata stored in the database.
Based on how things changed with VMM 2012 compared with 2008, you will have several new options and capabilites in the profiles for 2012.
I would recommend you to re-create those (hardware profiles, guest os profiles, application profiles etc) in 2012, as there is no logical mapping from the previous versions.
-kn
Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

Migration from SBS 2003 to Server 2008

Couple things. First, I wouldn't bother with 2008 at this point. Here's a pretty handy guide for 2012R2.
http://community.spiceworks.com/how_to/57636-migrate-active-directory-from-server-2003-to-server-201...
Second, I'd switch them over to hosted Exchange.
Did you spec your server already?

Hi guys,Very new to dealing with servers too much so please excuse any lack of info/dumb questions!I have been tasked to do a server migration for a small business. The details I know thus far (more to follow soon) are:There is currently only one server. It is running SBS 2003. It functions as a domain controller, and provides AD, DNS, exchange, DHCP and file sharing services. It is a physical server (Dell I believe). They want to move to another physical server running Windows Server 2008.There are around 15 users/terminals.There is a VLAN set up, not sure how yet. The VLAN needs to 'have a strong connection because heavy architect software needs to be used'Here is the plan of action I have so far:Ensure licenses for win server and exchange are bought.Install OS on new server, install all updates, service packs etc.Configure AD...
This topic first appeared in the Spiceworks Community

Active Directory not replicating from SBS 2003 to Server 2008 R2 Standard

I have an old SBS 2003 server and am migrating to a 2008 R2 server. I followed this guide:
http://demazter.wordpress.com/2010/04/29/migrate-small-business-server-2003-to-exchange-2010-and-windows-2008-r2/
I followed the guide (except the exchange stuff, because they are moving from exchange to Google apps for business) and everything went fine.
I removed the sbs from Domain controller status (dcpromo'ed it out) and everything seemed to go fine. I haven't turned off the old server yet, because they are still using it for a couple of other unrelated applications.
After I did this I added new computers to active directory, but they only showed up on the active directory on the old sbs (I think something went wrong when I too the old sbs out of domain controller status).
I ran dcdiag on the new server and this is the result:
  Time Generated: 01/10/2014   14:57:56
            Event String:
            The SiSRaid4 service failed to start due to the following error:
         An error event occurred. EventID: 0xC0001B58
            Time Generated: 01/10/2014   14:57:56
            Event String:
            The stexstor service failed to start due to the following error:
         An error event occurred. EventID: 0xC0001B58
            Time Generated: 01/10/2014   14:57:56
            Event String:
            The vhdmp service failed to start due to the following error:
         An error event occurred. EventID: 0xC0001B58
            Time Generated: 01/10/2014   14:57:56
            Event String:
            The vsmraid service failed to start due to the following error:
         A warning event occurred. EventID: 0x8000001D
            Time Generated: 01/10/2014   14:58:00
            Event String:
            The Key Distribution Center (KDC) cannot find a suitable certificate
to use for smart card logons, or the KDC certificate could not be verified. Sma
rt card logon may not function correctly if this problem is not resolved. To cor
rect this problem, either verify the existing KDC certificate using certutil.exe
or enroll for a new KDC certificate.
         An error event occurred. EventID: 0x0000164A
            Time Generated: 01/10/2014   14:58:20
            Event String:
            The Netlogon service could not create server share C:\Windows\SYSVOL
\sysvol\PIIKANIPW.local\SCRIPTS. The following error occurred:
         An error event occurred. EventID: 0xC0001B58
            Time Generated: 01/10/2014   14:58:21
            Event String:
            The Qntm3520 service failed to start due to the following error:
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   14:58:36
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved. This issue may be
transient and could be caused by one or more of the following:
         A warning event occurred. EventID: 0x00002724
            Time Generated: 01/10/2014   14:58:40
            Event String:
            This computer has at least one dynamically assigned IPv6 address.For
reliable DHCPv6 server operation, you should use only static IPv6 addresses.
         A warning event occurred. EventID: 0x800013B8
            Time Generated: 01/10/2014   14:58:49
            Event String:
            The application '/tmsWebAgent' belonging to site '1' has an invalid
AppPoolId 'Classic .NET AppPool' set. Therefore, the application will be ignore
d.
         A warning event occurred. EventID: 0x80003BC4
            Time Generated: 01/10/2014   15:01:53
            Event String:
            SSL Certificate Settings deleted for Port : 0.0.0.0:50106 .
         A warning event occurred. EventID: 0x80003BC5
            Time Generated: 01/10/2014   15:01:53
            Event String:
            SSL Certificate Settings created by an admin process for Port : 0.0.
0.0:50106 .
         An error event occurred. EventID: 0xC0001B7A
            Time Generated: 01/10/2014   15:01:59
            Event String:
            The TMS Print Agent service terminated unexpectedly. It has done th
is 1 time(s).
         A warning event occurred. EventID: 0x0000000C
            Time Generated: 01/10/2014   15:02:00
            Event String:
            Time Provider NtpClient: This machine is configured to use the domai
n hierarchy to determine its time source, but it is the AD PDC emulator for the
domain at the root of the forest, so there is no machine above it in the domain
hierarchy to use as a time source. It is recommended that you either configure a
reliable time service in the root domain, or manually configure the AD PDC to s
ynchronize with an external time source. Otherwise, this machine will function a
s the authoritative time source in the domain hierarchy. If an external time sou
rce is not configured or used for this computer, you may choose to disable the N
tpClient.
         An error event occurred. EventID: 0x0000165B
            Time Generated: 01/10/2014   15:02:34
            Event String:
            The session setup from computer 'PK-PC1' failed because the se
curity database does not contain a trust account 'PK-PC1$' referenced by t
he specified computer.
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   15:03:37
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved. This issue may be
transient and could be caused by one or more of the following:
         A warning event occurred. EventID: 0x000727AA
            Time Generated: 01/10/2014   15:04:01
            Event String:
            The WinRM service failed to create the following SPNs: WSMAN/PKDC01.
PIIKANIPW.local; WSMAN/PKDC01.
         A warning event occurred. EventID: 0x80003BC4
            Time Generated: 01/10/2014   15:06:54
            Event String:
            SSL Certificate Settings deleted for Port : 0.0.0.0:50106 .
         A warning event occurred. EventID: 0x80003BC5
            Time Generated: 01/10/2014   15:06:54
            Event String:
            SSL Certificate Settings created by an admin process for Port : 0.0.
0.0:50106 .
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   15:08:37
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved. This issue may be
transient and could be caused by one or more of the following:
         An error event occurred. EventID: 0x000016AD
            Time Generated: 01/10/2014   15:13:21
            Event String:
            The session setup from the computer PK-PC1 failed to authentic
ate. The following error occurred:
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   15:13:38
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved. This issue may be
transient and could be caused by one or more of the following:
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   15:18:39
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved. This issue may be
transient and could be caused by one or more of the following:
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   15:20:28
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved. This issue may be
transient and could be caused by one or more of the following:
         An error event occurred. EventID: 0x00000457
            Time Generated: 01/10/2014   15:20:33
            Event String:
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   15:23:39
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved. This issue may be
transient and could be caused by one or more of the following:
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   15:28:40
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved. This issue may be
transient and could be caused by one or more of the following:
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   15:33:41
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved. This issue may be
transient and could be caused by one or more of the following:
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   15:38:41
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved.
         ......................... PKDC01 failed test SystemLog
      Starting test: VerifyReferences
         ......................... PKDC01 passed test VerifyReferences
   Running partition tests on : DomainDnsZones
      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test
         CrossRefValidation
   Running partition tests on : ForestDnsZones
      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test
         CrossRefValidation
   Running partition tests on : Schema
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
   Running partition tests on : Configuration
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
   Running partition tests on : PIIKANIPW
      Starting test: CheckSDRefDom
         ......................... PIIKANIPW passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... PIIKANIPW passed test CrossRefValidation
   Running enterprise tests on : PIIKANIPW.local
      Starting test: LocatorCheck
         ......................... PIIKANIPW.local passed test LocatorCheck
      Starting test: Intersite
         ......................... PIIKANIPW.local passed test Intersite
I also noticed that the SYSvol share on the new server is empty and the NETLOGON share doesn't exist.
Please help! Thanks.

Hi,
Do you currently have any relevant errors in your System or Application logs?
Seems like the replication is not successfully.
An SBS server shouldn't shut down upon detecting the existence of another DC as that's a fully supported scenario.
Regards.
Vivian Wang

Migrating PDC role from SBS 2008 to Server 2012

Similar Messages

Maybe you are looking for