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

Similar Messages

  • 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

  • SBS 2003 to Server 2008/Exchange 2007

    We are in the process of moving our location and are in need of moving
    from SBS to something with more CALs.  I want to make this as seemless
    as possible for the end-users.
    We are currently on SBS 2003.
    My plan:
    Purchase new 64 bit server with Server 2008 and Exchange 2007.
    Add new server to existing domain.
    Move/migrate exchange from SBS to new server.
    Make sure the user info and and Group profiles move to the new server
    (not sure how to do that)
    Remove the SBS, and promote the new 2008 to DC.
    Possibly rename the 2008 to the same name and IP as the old SBS (so
    outlook users do not have to change anything)
    Would that be the correct route?  If so, what am I missing?  (Looks
    easy on paper)
    Thanks,
    Mike

    hi
    here is  a lead
    Start by installing Windows Server 2008 on the server you’re intending on using for mail. In our example we installed all the Exchange functionality on a single server – in practice you’ll probably want to separate out the Hub and Storage
    functions, and use a separate Edge server for mail traffic and user access to mail. There’s no problem with connecting to the network while you’re doing the install – Windows Server 2008 installs as a workgroup server – and you’ll
    automatically be delivered the latest drivers and the most up to date OS patches. You’ll also need to give the server an appropriate fixed IP address, as it’s going to become a key component of the network infrastructure.on the role and feature-based
    install model introduced with Windows Server 2003 and enhanced in Windows Server 2003 R2. Make sure you use these tools to install Internet Information Server – as Exchange 2007 will use it for Outlook Web Access and Exchange ActiveSync. Exchange 2007
    requires that servers have the PowerShell management scripting environment and the
    .NET framework. We’d also recommend installing Terminal Services as part of any Windows Server installation, as using Remote Desktop to access the new server and the existing SBS 2003 domain controller will let you handle much of the
    migration process from the comfort of your desk.Once Windows Server 2008 has been installed, take out the install DVD and shut the server down. As you’re going to be adding a Windows Server 2008 machine to what’s really a Windows Server 2003 network,
    you need to upgrade the Active Directory schema on our SBS 2003 server. This will allow you to manage the Windows Server 2008 machine from the SBS 2003 machine. You may need to update your version of Remote Desktop to one that supports the latest versions
    of the RDP protocol.Put the Windows Server 2008 DVD in your SBS 2003 machine’s DVD drive (a network accessible DVD drive is suitable, especially if access to any machine room is limited, and you’re using Remote Desktop to manage
    the server). Open a command line and change directory to SOURCES\ADPREP. You need to use ADPREP.EXE to update the Active Directory schema. Start by typing the following command to update the Active Directory forest.adprep.exe /forestprep.This will
    begin the process of updating the schema. Be prepared to wait some time, especially if you’re working with SBS 2003 rather than SBS 2003 R2. Once the forest schema has been updated you can update the domain schema. Type the following command:adprep.exe
    /domainprep.You’re now ready to bring the new Windows Server 2008 machine into your existing domain. Turn on the server, and then log in as a local administrator. Again, you can use Remote Desktop to work with the server, so you don’t need
    to sit in the machine room.to the existing SBS-managed domain. Once the server is part of the domain, you will to promote it from a member server to a domain controller. Launch DCPROMO
    using the Start menu search bar to find the program. Choose to add a domain controller to an existing domain. You’ll need to use the credentials of an existing domain administrator to start the process.Make the server a Global Catalog server.
    If you’re going to be keeping the existing SBS 2003 system there’s no need to make the new server a DNS server. DCPROMO will then add the requisite Active Directory Domain Services to your Windows Server 2008 machine. This can take some time, especially
    if you’re working with a large SBS-managed network with more than 50 users. Once the DCPROMO process is complete you’ll need to restart the server. You can now log in as a domain administrator.Now you can start the process of installing Exchange
    2007 on the new server. There’s one key issue that needs to be dealt with first. Exchange 2007 needs to install on a server that’s a Schema Master.
    One of the limitations of SBS 2003 is that the SBS server needs to own all five of the FSMO
    roles. The Flexible Single Master Operations are key domain management tasks, and in a standard Active Directory implementation, these roles can be parcelled out across several servers. Microsoft’s restrictions on SBS can be overcome –
    as the SBS licence allows FSMO roles to be temporarily transferred to other servers for the purpose of server migration and major hardware upgrades. You can continue to run SBS for up to seven days (there is an option to install an update that extends this
    to 21 days) with the FSMO roles on other servers. Don’t let the migration drag on as after that point, the server will reboot every hour, until the roles are transferred back.You’ll need to be logged in to your SBS server to move the Schema Master
    to the Windows Server 2008 machine. Start by registering SCHMMGMT.DLL. This allows you to use the Windows Schema Master management tools to transfer the Schema Master role to the Windows Server 2008 machine. Open a command line and type the following command.regsvr32
    schmmgmt.dll
    You’ll next need to open the Windows Management Console. Once you’ve done this, by typing
    mmc at a command prompt or from the Run option on the start menu, you can load the Active Directory Schema management snap-in. From the File menu click Add/Remove Snap-in. This opens a dialog box where you can choose to add the appropriate
    tools. Choose Active Directory Schema. This will load the schema management tools, which you can use to move the Schema Master to a new machine.In the Schema Manager console, right click on Active Directory Schema and then choose Change Domain Controller.
    You’ll see a list of available servers. Choose the new Windows Server 2008 machine, and then click Change to move the Schema Master role to your new Exchange machine. Right click Active Directory Schema again, and choose Operations Master. This allows
    you to make the new server the operations master for the FSMO role we’ve just transferred.
    Now you can start the Exchange 2007 installation. Log on to the server, and load the Exchange 2007 DVD; using an Exchange 2007 SP1 DVD reduces the amount of time you’ll need to set aside for downloading and installing uploads. Choose the appropriate Exchange
    installation for your network needs – a typical install with Hub Transport, Client Access and Mailbox roles should be sufficient for most small networks. Once Exchange has installed, restart the Windows Server 2008 machine and then open the Exchange
    Management console to confirm that your install completed successfully.You will now have added your new Exchange server to the existing SBS Exchange network. On the SBS server open the Exchange System Manager.Expand the Administrative Groups tab to see the
    available administrative groups. Your new server should have added itself as Exchange Administrative Group (FYDIBOHF23SPDLT). Do not move it out of this Administrative Group or the associated routing group, Exchange Routing Group (DWBGZMFD01QNBJR) –
    these are required to allow Exchange 2007 to interoperate with Exchange 2003. (As a side note, there’s definitely a sense of humour in the Exchange team at Microsoft, as the default administrative group and routing group names are both Caesar Ciphers
    of EXCHANGE12ROCKS).If you’re planning to run the two servers together, you can now move the Schema Master FSMO role back to the SBS server; if you’re not, you now have seven days to finish your complete server migration before the reboots start.
    To move the role back use the Active Directory Schema MMC snap-in and change both Domain Controller and Operations Master to point to your SBS server.Now you can start to move mailboxes between the two servers. This is where things can start to take time,
    so schedule mailbox moves for evenings and weekends – and make sure that you’ve backed up all the existing mailboxes before you start the migration.
    You’ll also need to make sure that both servers have the same mailbox size limits – otherwise large mailboxes will fail to move successfully. If you’re unable to make moves at night, you can do them during working hours –
    but users will be unable to connect to the Exchange server while their mailboxes are being transferred (remember to warn them in advance). Any mail that’s been delivered to the server during a mailbox transfer will be queued and delivered once the mailbox
    is on the new server.
    The actual process of moving mailboxes from the SBS Exchange 2003 server to Exchange 2007 is relatively simple. Log on to your Exchange 2007 server, and open the Exchange Management Console. Expand Recipient Configuration, and select the Mailbox
    view. This lets you see the organisation’s mailboxes, along with where they’re currently stored. A pane on the right gives you various Actions you can perform on the mailboxes. These include the Move Mailbox wizard.
    This wizard is the simplest way of moving mailboxes between servers – and, along with the underlying move – Mailbox PowerShell commandlet, is the only supported way of moving mail to an Exchange 2007 server. If you’re moving a large set of
    mailboxes it’s worth writing a PowerShell script to handle the move for you.
    Use the Move Mailbox wizard to move either an individual mailbox or groups of mailboxes (shift-click to select several at once). As the wizard is multi-threaded it can handle up to four mailbox moves at once. First select the target database, and then choose
    the move options. You can choose to abort the move if corrupted messages exist, as well as choosing the appropriate Active Directory servers. You can also schedule the moves for out of hours – so you don’t have to be on site for a move to take
    place – as well as making sure that any moves that haven’t taken place inside a set time limit are cancelled. The wizard will check mailbox quotas before making a move to make sure that the system limits allow the mailbox to transfer to a new server.
    Once a move’s started you’ll see a progress bar showing the status of the move, with descriptive text for the current step in the move process. When a move completes there’s a summary screen with the results. There’s also an XML
    format report you can use for further analysis.
    We found that a large 4GB mailbox took about 3 hours to move, over a gigabit network. In practice, most mailboxes are a lot smaller, so expect to be able to move many more SBS mailboxes in a single overnight session. Once the mailboxes have been moved, your
    Outlook users will automatically be switched to the new Exchange server. There’s no need to change anything on the desktop – the Exchange organisation will handle the changes for you. There’s one exception; if you have used a self-certified
    certificate for the SBS Exchange server, you may need to delete it from all client devices (including Windows Mobile) so they can connect – especially if you’re using the same external DNS name.While Outlook handles the changes gracefully, things
    aren’t so easy for users working with ActiveSync connections to mobile devices or for secure IMAP and POP3
    connections. Mobile users will need to perform a manual sync on their phone (they’ll get a message in ActiveSync reminding them to do this) and accept the server policies before mail will start arriving. POP3 and IMAP connections will only continue
    to work if you make sure that your new mail server has the same external CNAME as the old SBS install. If you’re not using the same DNS name, you’ll need to recreate connections for external mail clients.
    Naeem Bhatti MCITP EA, MCITP, MCTS Exchange 2007 MCSE security,MCSE AD, MCSE in Messaging, MCDST SBS2003 and SBS2008 Specialist

  • Migrating DHCP Server From OpenSuse to Windows Server 2008 R2 Standard

    Hello,
    I'm planning to migrate a DHCP server from OpenSuse to Windows Server 2008.
    Is there any procedures for that ,Or should i configure my Windows server 2008 DHCP service again.
    Thank you 

    Hi,
    I have done somthing similar in the past. Basically i got exported all the scopes and settings from the linux dhcpd service, then created the scopes in Windows, stop linux dhcp service and start windows one. Use conflict detection setting to leverage any
    IPs lease from linux server.
    Hope it helps.
    Regards,
    Calin

  • Active Directory Not Replicating

    Hey Guys,
    I have a Windows 2012 server but it has a demo license, this is also my DC. I am trying to create another DC and let it replicate so I can license the new properly and stuff. I have the DNS of each server pointing to each other as the primary and themselves
    as the alternative. When I check my SYSVOL folder and go to domains, its empty, as I shutdown my original DC the other one the entries disappear and I get errors. When I go to the event log on my new DC I get errors with event IDs 1202 and 2213. Any assistance
    with this issue i'm having will be greatly appreciated, thanks!
    Regards,
    Jevon.

    Please follow this , it should help  expecially this section:
    For environments that have two domain controllers 
    Determine whether a dirty shutdown was detected (event ID 2213) on either domain controller. You may find the second domain controller
    is waiting to complete initialization of SYSVOL, This is because after promotion, it will have logged a 4614 event that indicates that DFS Replication is waiting to perform initial replication, and it will not have logged a 4604 event signaling that
    DFS Replication has initialized SYSVOL.
    If content freshness is enabled on both domain controllers
    If the second domain controller is waiting to perform initial synchronization (event 4614 logged without the 4604 anti-event), follow
    the section of article 2218556 to
    set the first domain controller as authoritative. You do not have to configure the second domain controller as nonauthoritative, because it is already waiting to perform initial synchronization.
    Or, if the second domain controller is healthy and SYSVOL is shared, perform the following steps:
    Back up all SYSVOL contents of the first domain controller.
    Evaluate if the second domain controller's SYSVOL data is up to date. If it is not, you may want to copy updated SYSVOL files to the second domain controller from the first domain controller. Otherwise, any existing data
    present on first domain controller not present on the second will go into the 'PreExisting' and 'Conflict and Deleted' folders.
    Set the first domain controller as nonauthoritative by disabling the membership per 2218556.
    Confirm that an event ID 4114 is logged to indicate the membership is disabled.
    Enable the first domain controller's membership, and wait for the 4614 and 4604 events that report completion of the initial synchronization. If it is necessary, restore any updated files from "PreExisting" to the
    original location.
    If content freshness is not enabled or triggered on both domain controllers
    If the first domain controller is in the event ID 2213 state and the second domain controller has never completed initialization
    after it was promoted and content freshness has not been triggered, perform the following steps:
    Run the ResumeReplication WMI method on the first domain controller as instructed in the 2213 event.
    After replication resumes, it will log an event ID 4602 that indicates that DFS Replication initialized the SYSVOL replicated folder and designated it as the primary member.
    Run the dfsrdiag pollad command on the second domain controller to trigger it to complete initial sync (event ID 4614). As soon as initial sync is finished, event ID 4604 is logged, signaling SYSVOL
    has completed initialization.
    Or, if the first domain controller is in the 2213 state and the second domain controller is healthy (SYSVOL is shared), run theResumeReplication WMI
    method on the first domain controller. It will log event ID 2214 at the completion of dirty shutdown recovery.  
    This post is provided AS IS with no warranties or guarantees, and confers no rights.
    ~~~
    Questo post non fornisce garanzie e non conferisce diritti

  • Configuration is not replicated from CRM to ECC for configurable product

    Hi,
    We have some materials in the system for which the configuration is not replicated from CRM to ECC.
    We create a quotation in CRM and configure it. In CRM,  the configuration is complete and components are properly exploded but when we check the same quotation in ECC, configuration is incomplete with respect to some characteristics and product references.
    Please find below finding
    1. If the same material is created in another plant/company code, the configuration is replicated properly.
    2. We have also checked that the BOM is completely maintained for plants for which configuration is replicated. But we dont think so it could be an issue since if we create the quotation in ECC instead of creating in CRM, for the plant (for which the configuration is not replicated from CRM to ECC),  it is properly exploded and complete.
    3. variant prices are replicated properly even though components are not replicated.
    We need to know if we can explode the BOM in the configuration even though complete BOM for the particular plant is not maintained. If its not possible to explode, why it is possible for us to explode the BOM in the configuration in quotation.
    Please  advise.
    Thx.

    the configuration (variant configuration and not customization) that is done in CRM contract is not copied to ECC contract. Is it because that item category in CRM is activated for doing the BOM configuration and the same in ECC is not activated for doing the BOM configuration?
    My question is that if item category in ECC is not activated for BOM configuration then is it like that the BOM configuration in CRM will not be copied to ECC?

  • Business partner(employee) is not replicated from ECC to CRM

    The Business partner Not replicated in CRM.Two Sales organization have been maintained for the employee for the different time lines in ECC.Checked the BDOCs and the validation error occur in FM CRM_BUPA_MAIN_VAL .The BDOCs message was saying the BPGUID was missing .Could anyone please suggest what could be the root cause of the data not replicated from ECC to CRM.

    Hi Pragnya,
    This is the case where at the time of creation of BP there was some issue with replication.
    The BP itself is not there in CRM or only the changes are not reflected?
    In such scenarios, perform following steps for successful replication:
    1. Go to TCode: CRMM_BUPA_MAP
    2. Enter the BP no. {initially it says it does not exist}
    3. Enter ERP customer no. and press enter, the BP GUID gets filled
    4. Click on "Gather Information about customer" [you can see the status of the object]
    5. Now again enter the BP no. -> The customer is available in CRM now.
    Regards,
    Swagi

  • Accidently removed a mailbox on the SBS 2008 server during the migration from SBS 2003

    I accidently removed a legacy mailbox from the SBS 2008 server while still doing the migration from SBS 2003.  I meant to click on the Move Mailbox like the instructions said but clicked on the Remove option, then clicked the 'X' to close the box since
    I figured that would cancel what I did however it removed the mailbox from the SBS 2008 list.
    Please tell me that I can get it back.  It still shows up in the old SBS Exchange System Manager but now when an email is sent, it sends back a no delivery message.  It's like the account doesn't exist any more.
    Can it be recovered and if so, how?
    thanks,
    Jeff

    Hi Jeff,
    Would you please let us know current situation of this issue? Just check if above suggestions can help you.
    If any update, please feel free to let us know.
    In addition, please also refer to following article and thread, and then check if can help you.
    How
    to use a Recovery Storage Group in SBS 2008
    How
    to recover a deleted user and mailbox on SBS 2008
    Hope this helps.
    Best regards,
    Justin Gu

  • I want to install XP Pro SP2 on a Mac Mini from a 2003 RIS server.

    I want to install XP Pro SP2 on a Mac Mini from a 2003 RIS server. Is this possiIble? How is it done?
    The mac has 10.5 which has bootcamp to enable Windows install. I have created a partition but the bootcamp utility asks for a CD. I want to install a RIS build. The Mac has a option for network boot but this seems to only work with Mac Server. I assume the network adapter is not PXE compatible and so a boot disk of some kind will be needed to kick this off?.

    Hallo, I installed the program as you said. Everything ok.
    When i have to give my serialnummer, it is not accepted. Code is not valid he said
    1160-4008-7475-7547-5706-0812
    Op 21-sep.-2014, om 17:44 heeft Rikk Flohr <[email protected]> het volgende geschreven:
    Hi, I want to install my lightroom version on a new mac pro. How do i get started. Can't find it on this site. Thx
    created by Rikk Flohr in Photoshop Lightroom - View the full discussion
    www.adobe.com
    Hit the Download link at the bottom the page.
    Hit Lightroom
    Hit Free Trial
    When you are done downloading, launch, and enter your serial number from your previous installation.
    Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at https://forums.adobe.com/message/6749435#6749435
    Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page:
    To unsubscribe from this thread, please visit the message page at . In the Actions box on the right, click the Stop Email Notifications link.
    Start a new discussion in Photoshop Lightroom by email or at Adobe Community
    For more information about maintaining your forum email notifications please go to http://forums.adobe.com/thread/416458?tstart=0.

  • Migrating dns from windows 2003 to windows 2008 on workgroup env

    Hi, We are planning to migrate primary dns server from win 2003 to win 2008. Both the old and new servers will be in work group. I have found few articles on how to proceed.
    1. Configure new dns server 2008 R2 box as a secondary zone and doing a zone transfer for froward & reverse lookups  from the primary Server 2003 machine. Then changing the name and IP of the Server 2008 R2 machine  to
    what the Server 2003 box was (after pulling the Server 2003 box off the network) as well as setting the 2008 R2 box as the primary. Neither of the servers will be connected to a domain at any point during or after this process.
    2. Copy registry keys and dns files from old to new server
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\DNS Server\Zones
    Right click on the “Zones” node and choose “Export“. Save the export as a .reg file (e.g. DNS.reg).
    Copy the DNS.reg file to the destination server and “Merge“.
    Copy the DNS files
    Copy the contents of the %SystemRoot%\System32\DNS folder from the source machine to the same folder on the destination machine. I received an permissions error while trying to transfer the “Samples” folder. It is not necessary to transfer the samples.
    Set the DNS Load method
    Using the Administrative Tools -> DNS MMC snap-in, on the “Advanced” tab, set the “Load zone data on startup:” to “From registry“. This tells the DNS server to load all zone data from the registry.
    Then change the ip address and hostname of the new server to match that of the old ones and start dns service.
    I was wondering which method would be easy and hassle free as I have like 23 zones to transfer.
    Any help would be appreciated.
    Thanks,
    Lakshmi Soma

    I would go with the first method as I always try to avoid making registry changes which might result in strange behaviors.
    This posting is provided AS IS with no warranties or guarantees , and confers no rights.
    Ahmed MALEK
    My Website Link
    My Linkedin Profile
    My MVP Profile

  • Problems Migrating from VS 2003 and CR 2008 to VS 2008

    I am in process of upgrading from VS 2003 to VS 2008.   At same time u2013 moving from Windows Xp to Windows 7.    I was using CR 2008 on the XP and also installed it on Win 7.   Now seems I have no support or SDK for VS 2008.   Even if I add a new Cr object u2013 the screen us blank.
    Any and all assistance would be greatly appreciated.
    What do I need to do to get this to work u2013 and be able to safely distribute the resulting project?  
    Would upgrading to SAP CR 2011 work coupled with downloading the SDK for VS 2010?  Or Reinstalling VS 2008?
    Thank you
    JimH

    Hi Jim,
    CR for VS 2010 will not work in VS 2008 and CR 2011 does not have an SDK install.
    If you have Installed CR 2008 before VS 2008 it won't be integrated into VS. Do a repair install of VS 2008 and that should fix VS, assuming CR 2008 is installed and it's not a CR 2008 Basic, must be higher to get the SDK to install and work. Go into Add/Remove Programs and select CR 2008 and change, use the Custom Option and you should see the option to add .NET. Sorry I don't recall the exact wordage, it's been a while since I installed it.
    And be sure to get the latest Service Packs for VS and CR 2008 SP 4. You can get them form the [download page|https://websmp230.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/spn/bobj_download/main.htm]
    Then check your references, they should be 12.x.x.xxxx and remove the 9.x from your project first if they are there still also. VS usually asks if you want to upgrade so I suspect a repair on CR and then possibly a repair in VS 2008 should fix the problem.
    Download page also has the Redist Packages to deploy your app and CR runtime also.
    Don

  • Can I create pdf files from Outlook 2003 messages with Acrobat XI Standard?

    Can I create pdf files from Outlook 2003 messages with Acrobat XI Standard?

    Yes, Outlook 2003 is compatible with Acrobat XI Standard and you can create PDFs from emails.
    For reference: http://helpx.adobe.com/acrobat/kb/compatible-web-browsers-pdfmaker-applications.html

  • My Canon MX310 Series Printer failed as the software "is currently not available from the Software Update Server"? What is the matter with Apple OSX Mountain Lion?

    Mountain Lion stopped working with our Canon MX310 Printer? Why is the software not available from the Software Update Server?

    The printer and ICA scanner driver is available from Apple. There is probably some other reason why you cannot get the drivers.
    You can also get the drivers from Canon.
    But reading your post it sounds like you were printing to the MX310 and recently it has stopped printing. Is this the case?

  • Conecting to the internet Via a SBS 2003 Windows server

    I have 2 macs connected through a 10/100 tbase switch and a SBS 2003 windows server also connected to the switch. The widows server is what accesses the internet. how do i get the macs to pick up the conection???

    Hi, and a warm welcome to the forums!
    http://www.chicagotech.net/icssetup.htm
    http://support.microsoft.com/kb/324286
    http://www.ifelix.co.uk/tech/index.html

  • Windows Server 2008 R2 Standard "Certificate Authority Service" / Exchange Server 2010 EMC not starting and no AD connectivity for authentication.

    Hello,
    I am a new IT Manager at this company and need assistance big time. Their environment looks as follows:
    Server 1. Domain Controller Server (Windows Server 2008 R2 Standard) running active directory.
    Server 2. Email Server (Windows Server 2008 R2 Standard) running Exchange Server 2010 .
    * Note. No back ups to work with aside from whats mentioned below.
    DC had a virus infection causing a lot of issues on the shared network drives 2 days ago locking up all the files with a crypto ransom virus. Running Avast suppressed the infection. Had to recover the file shares which luckily had a back up. 
    The issue is that the Exchange Server 2 post this lost connectivity with the AD Server 1. Exchange Server 2 when launching EMC could not launch the console stating the following:
    "No Exchange servers are available in any Active Directory sites. You can’t connect to remote
    Powershell on a computer that only has the Management Tools role installed."
    Shortly after I found that it is possible the EMC launcher was corrupt and needed to be reinstalled following another blog post. I deleted the exchange management console.msc  per instructions only to discover I couldnt relaunch it because there was
    no way how. So I copied another msc file that happened to be on the DC Server 1  back to Exchange Server 2 and got it to launch again. 
    Another post said that it might be an issue with the Domain Account for the Computer, so to delete it in the AD Server 1 only to find that rejoining it from Exchange Server 2 using Computer>Properties> Chage Settings > Change is greyed out because
    it is using the Certificate Authority Service.
    I tried manually re-adding the computer in AD and modeling permissions after another server in group settings but no go. After this I was unable to login to the Exchange Server 2 with domain accounts but only local admin, receiving the following Alert:
    "The Trust Relationship between this workstation and primary domain failed."
    I tried running the Power Shell tools on Exchange Server 2 to rejoing and to reset passwords for domain accounts as noted in some other blogs but no luck as the Server 2 could not make the connection with Server1 or other errors it kept spitting out.
    I also during the investigation found the DNS settings were all altered on both the Server 1 and Server 2 which I luckily was able to change back to original because of inventorying it in the beginning when I started. 
    I need help figuring out if I need to rejoin the Exchange Server 2 manually by disabling the Certificate Authority Service (or removing the CA as listed here:
    https://social.technet.microsoft.com/Forums/exchange/en-US/fb23deab-0a12-410d-946c-517d5aea7fae/windows-server-2008-r2-with-certificate-authority-service-to-rejoin-domain?forum=winserversecurity
    and getting exchange server to launch again. (Mind you I am relatively fresh to server managing) Please help E-Mail has been down for a whole day now!
    Marty

    I recommend that you open a ticket with Microsoft Support before you break things more.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Maybe you are looking for