Migrating Server 2003 to Server 2008 R2

I am in migration hell... the network is a simple one, it has one domain controller running a Windows Server 2003 domain in Windows 2000 Native mode.  No other servers but a NAS box are on the network, the rest are workstations. I am migrating it to
a Windows Server 2008 R2 x64 bit server, I used adpre32 to perform the steps on the old server.
Before performing the migration I ran netdiag and dcdiag and came up clean. I ran the adprep steps and everything ran great. I got to the part where I was going to transfer the roles and ntdsutil gives a "connect to server WIN2008SERVERNAME, that's
when I get the binding error "ntdsutil dsbind error 0x5 access is denied".
When I also try to go in via Active Directory Users and Computers (on the original domain controller) and then try to connect to a Domain Controller, I see the new DC but when I go to select it I get "The following domain controller could not be
contacted : WIN2008SERVERNAME.DOMAINNAME.COM Access is denied.
I have run repadmin /showrepl on the original box and it came back as successful. I ran DCDIAG and came up fine. I ran nltest /sc_query:DOMAINNAME.COM which came back as I_NetLogonControl failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN.
Network browsing works fine, all computers logon fine and nslookup runs on both the old server and new one showing the old server as it should until the FSMO roles get transferred.
All of this works fine form the new server, DNS looks good and dcdiag DNS testing came up fine. I'm basically banging my head against a wall at this point. 

Here are the NETDIAG results from the source domain controller, notice towards the end where it states that LDAP passed but had fatal errors. This is whats blocking the roles from being transferred. I admit I am lacking the knowledge to repair this
so I appreciate the help.
        KB2898715
        KB2898860
        KB2900986
        KB2901115
        KB2904266
        KB2909210-IE8
        KB2914368
        KB2916036
        KB2922229
        KB2923392
        KB2927811
        KB2929961
        KB2930275
        KB2936068-IE8
        KB921503
        KB923561
        KB925398_WMP64
        KB925876
        KB925902
        KB926122
        KB927891
        KB929123
        KB930178
        KB931768
        KB931784
        KB931836
        KB932168
        KB933360
        KB933566
        KB933566-IE7
        KB933729
        KB933854
        KB935839
        KB935840
        KB935966
        KB936021
        KB936357
        KB936782
        KB937143-IE7
        KB938127-IE7
        KB938464
        KB939653-IE7
        KB941202
        KB941568
        KB941569
        KB941644
        KB941672
        KB941693
        KB942615-IE7
        KB942763
        KB943055
        KB943460
        KB943484
        KB943485
        KB943729
        KB944533-IE7
        KB944653
        KB945553
        KB946026
        KB947864-IE7
        KB948496
        KB948590
        KB948881
        KB949014
        KB950759-IE7
        KB950760
        KB950762
        KB950974
        KB951066
        KB951072-v2
        KB951698
        KB951746
        KB951748
        KB952004
        KB952069
        KB952954
        KB953298
        KB953838-IE7
        KB953839
        KB954155
        KB954211
        KB954550-v5
        KB954600
        KB955069
        KB955759
        KB955839
        KB956390-IE7
        KB956391
        KB956572
        KB956744
        KB956802
        KB956803
        KB956841
        KB956844
        KB957095
        KB957097
        KB958215-IE7
        KB958644
        KB958687
        KB958690
        KB958869
        KB959426
        KB960225
        KB960714-IE7
        KB960715
        KB960803
        KB960859
        KB961063
        KB961260-IE7
        KB961371
        KB961371-v2
        KB961373
        KB961501
        KB963027-IE7
        KB967715
        KB967723
        KB968389
        KB968537
        KB968816
        KB969059
        KB969805
        KB969897-IE7
        KB969897-IE8
        KB969898
        KB969947
        KB970238
        KB970430
        KB970653-v3
        KB971029
        KB971032
        KB971468
        KB971486
        KB971557
        KB971633
        KB971657
        KB971737
        KB971930-IE8
        KB971961-IE8
        KB972260-IE8
        KB972270
        KB973037
        KB973346
        KB973354
        KB973507
        KB973525
        KB973540
        KB973687
        KB973815
        KB973825
        KB973869
        KB973904
        KB974112
        KB974318
        KB974392
        KB974455-IE8
        KB974571
        KB975025
        KB975467
        KB975558_WM8
        KB975560
        KB975713
        KB976098-v2
        KB976662-IE8
        KB976749-IE8
        KB977165
        KB977290
        KB977816
        KB977914
        KB978037
        KB978207-IE8
        KB978251
        KB978262
        KB978338
        KB978542
        KB978695
        KB978706
        KB979306
        KB979309
        KB979482
        KB979687
        KB979907
        KB980232
        KB982132
        Q147222
Netcard queries test . . . . . . . : Passed
Per interface results:
    Adapter : Local Area Connection
        Netcard queries test . . . : Passed
        Host Name. . . . . . . . . : SPNET01
        IP Address . . . . . . . . : 192.168.100.2
        Subnet Mask. . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . : 192.168.100.1
        Dns Servers. . . . . . . . : 192.168.100.2
                                     192.168.100.4
        AutoConfiguration results. . . . . . : Passed
        Default gateway test . . . : Passed
        NetBT name test. . . . . . : Passed
        [WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenge
r Service', <20> 'WINS' names is missing.
            No remote names have been found.
        WINS service test. . . . . : Skipped
            There are no WINS servers configured for this interface.
Global results:
Domain membership test . . . . . . : Passed
NetBT transports test. . . . . . . : Passed
    List of NetBt transports currently configured:
        NetBT_Tcpip_{A759140A-13DA-481A-8BCB-47F2A6EB9EAF}
    1 NetBt transport currently configured.
Autonet address test . . . . . . . : Passed
IP loopback ping test. . . . . . . : Passed
Default gateway test . . . . . . . : Passed
NetBT name test. . . . . . . . . . : Passed
    [WARNING] You don't have a single interface with the <00> 'WorkStation Servi
ce', <03> 'Messenger Service', <20> 'WINS' names defined.
Winsock test . . . . . . . . . . . : Passed
DNS test . . . . . . . . . . . . . : Passed
    PASS - All the DNS entries for DC are registered on DNS server '192.168.100.
2' and other DCs also have some of the names registered.
    PASS - All the DNS entries for DC are registered on DNS server '192.168.100.
4' and other DCs also have some of the names registered.
Redir and Browser test . . . . . . : Passed
    List of NetBt transports currently bound to the Redir
        NetBT_Tcpip_{A759140A-13DA-481A-8BCB-47F2A6EB9EAF}
    The redir is bound to 1 NetBt transport.
    List of NetBt transports currently bound to the browser
        NetBT_Tcpip_{A759140A-13DA-481A-8BCB-47F2A6EB9EAF}
    The browser is bound to 1 NetBt transport.
DC discovery test. . . . . . . . . : Passed
DC list test . . . . . . . . . . . : Passed
Trust relationship test. . . . . . : Skipped
Kerberos test. . . . . . . . . . . : Passed
LDAP test. . . . . . . . . . . . . : Passed
    [FATAL] Cannot do NTLM authenticated ldap_bind to 'SPNET08R2.SPNET.com': Inv
alid Credentials.
    [FATAL] Cannot do Negotiate authenticated ldap_bind to 'SPNET08R2.SPNET.com'
: Invalid Credentials.
    [WARNING] Failed to query SPN registration on DC 'SPNET08R2.SPNET.com'.
Bindings test. . . . . . . . . . . : Passed
WAN configuration test . . . . . . : Skipped
    No active remote access connections.
Modem diagnostics test . . . . . . : Passed
IP Security test . . . . . . . . . : Skipped
    Note: run "netsh ipsec dynamic show /?" for more detailed information
The command completed successfully
C:\>

Similar Messages

  • Migrate Server 2008 Certificate Authority To New Server Different Host Name?

    Our internal CA is installed on one of our Exchange servers.  Exchange is being migrated from 2010 to 2013, so all current Exchange servers will decommissioned and replaced with new new Hyper-V VMs with either Server 2008 R2 or 2012 R2 OS. The old VM
    containing Exchange 2010 and the current CA will go away since we cannot afford to use the server resources and use up the required Windows license to keep that server running doing nothing but acting as a CA.
    So, we will either need to move the CA to the new replacement Exchange 2013 server or some other existing server that's being used for something else (maybe one of the domain controllers).
    What is the best way to handle this?  I don't think the migration from Exchange 2010 to 2013 allows for reusing the same host name on the replacement server and if we move the CA to another existing server, it will also be on a server with a new host
    name anyways.
    Can we migrate the CA to a new server with a different host name?
    What about reissuing all the active certificates from the current server to replace them with new certificates from the new server and then decommissioning the original CA?  Can this be automated in some way?
    Which way is best and how would it be done?

    When following the instructions in the guide, I would also consider to switch to new "sanitized" URLs in certificates (CDP and AIA) in case you had used the default URLs now. That's what I did this when migrating W2K3 CAs (with default URLs) to W2K8 R2.
    Per default, the LDAP and HTTP URLs point to the CA server itself (HTTP) or to an LDAP objects that has the same name as the current server.
    Migrating to a new server, you need to make sure that CRLs will still be published to the old locations - thus the new CA server would write to the LDAP object that corresponded to the old server, and HTTP might be fixed by redirecting the DNS record. (Make
    sure this is documented so that nobody thinks it might be a good idea to delete the old object as it "references a server that does not exist anymore".)
    As you have to fiddle with URLs anyway, I would then add new URLs having neutral names - that is URLs not including the name of the CA server. The new CA instance would then 1) publish to the old locations but not add these to certificates anymore and 2)
    publish to new sanitized locations and add them to CDP and AIA URLs.
    Elke

  • PKI migration from 2003 to greenfield 2008 R2 plan-of-approach

    Hi,
    I've done a lot of reading here already but I'm on a dead end. Here's my scenario:
    I have 1 Stand-alone root CA plus 2 Enterprise issuing CA's, all running Windows Server 2003. I'm trying to move all servers to a new OS platform: Server 2008 R2. The way I'm seeing this is I have to migrate the Root CA first, then all issuing CA's, so my
    first question is:
    1. Is this correct?
    I followed this procedure:
    http://technet.microsoft.com/en-us/library/cc742388(v=ws.10).aspx. At "To set up a CA on a computer running Windows Server 2008" I specified the backup I made earlier and specified the private key from the 2003 stand-alone root CA. After
    the wizard finishes, I am able to succesfully start the CA on the 2008 server. Next chapter is "Restoring the database and configuration on the target computer". It prompts to shut down the CA service, which I allow, it restores the DB (which
    I point to as part of the wizard), when it finishes restoring, it prompts to start the CA service again. This is where the headache starts; it throws an ADCS error "0xc8000220 (ESE: -544)" and it fails to start.
    The application log on the target server throws the following errors (in chronological order) :
    [source: ESENT - EventID: 916] certsrv.exe attempted to attach database 'C:\windows\system32\certlog\<CANAME> but it is a database restored from a backup set on which hard recovery was not started or did not complete successfully'
    [source: CertificationAuthority - EventID: 17] "Active Directory Certificate Services did not start: Unable to initialize the database connection for <CANAME>. Error: 0xc8000220 (ESE: -544).
    I have no idea as to what this means so my next Obvious question would be:
    2. Please advice in my next step?
    Cheers!
    Check out my blog you-n-it.net

    Kurt,
    Thanks for your reply.
    Unfortunately I'm still not able to migrate an out-of-the-box stand-alone root CA 2003 to a 2008 server. Using the same or another host name. I'm at a dead end. One thing I noticed is:
    When running esentutl /g on the running CA DB (in a lab) things are ok. Running it on the back-upped version of the db, it says it's corrupted. esentutl /r does NOT repair it. esentutl /p does, and afterwards it's verifiable using esentutl /g but it's still
    not possible to bring it online. I've followed
    http://technet.microsoft.com/en-us/library/cc742388(v=ws.10).aspx to the letter and I've read other sites as a comparison (not doubting, merely looking for success stories based on this procedure) and it seems like I'm the only one in the world that's unable
    to perform a successful restore! :( Anywhere I can dig deeper?
    This error is my nemesis: [ESENT: 412] certsrv.exe (2824) Restore0001: Unable to read the header of logfile C:\Windows\system32\CertLog\edb00003.log. Error -546.
    Cheers!
    Check out my blog you-n-it.net

  • Stuck at restoring print queues while migrating from 2003 X86 to 2008 R2

    i am trying to migrate from 2003 to 2008 R2 but i am stuck where it says restoring print queues and is tuckat 84% there is no error and it has not completed from pas 3 hrs now.. i have 6 print queues on it and is it normal that this willtake such long for
    these 7 queues

    we are getting the following error.
    Log Name: Application Source: Microsoft-Windows-PrintBRM Date: 1/23/2014 5:27:15 PM Event ID: 30 Task Category: (5) Level: Error Keywords: Classic User: N/A Computer: MARPRINTPC01N1.bsci.bossci.com Description: The language monitors in the backup file
    are for a different processor architecture than the destination computer. Printbrm.exe (the Printer Migration Wizard or the command-line tool) will not migrate any language monitors. Source architecture: Windows NT x86. Destination architecture: Windows x64.
    Event Xml: <event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><system></system><provider EventSourceName="PrintBrm" Guid="{CF3F502E-B40D-4071-996F-00981EDF938E}" Name="Microsoft-Windows-PrintBRM"></provider><eventid Qualifiers="49154"></eventid>30</eventid><//eventid>
    <version></version>0</version><//version> <level></level>2</level><//level> <task></task>5</task><//task> <opcode></opcode>0</opcode><//opcode> <keywords></keywords>0x80000000000000</keywords><//keywords> <timecreated SystemTime="2014-01-23T22:27:15.000000000Z"></timecreated><eventrecordid></eventrecordid>4174</eventrecordid><//eventrecordid>
    <correlation></correlation><execution ProcessID="0" ThreadID="0"></execution><channel></channel>Application</channel><//channel> <computer></computer>MARPRINTPC01N1.bsci.bossci.com</computer><//computer> <security></security></system><//system><eventdata></eventdata><data
    Name="param1"></data>Windows NT x86</data><//data> <data Name="param2"></data>Windows x64</data><//data> </eventdata><//eventdata></event>

  • CA Server Migration from 2003 R2 to 2008 R2

    What would be the best path to upgrade the Certification Authority (CA) server for a domain that is currently running off Windows Server 2003 R2?
    1. In-place upgrade to 2008
    2. Backup existing configuration, decommission server from domain, bring a 2008 R2 server online to the domain with the same name and then restore configuration

    Hello,
    is that a single server domain? So everything is installed on a single DC?
    Best regards
    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://blogs.msmvps.com/MWeber
    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
    Twitter:  

  • Migrating from 2003 DC to 2008

    I have been working on cleaning up a network that I inherited.  Currently we are running at a 2003 function level and I want to bump that up to 2008.  
    At our main site I have 3 Domain Controllers, 2 are 2008 and 1 is 2003.  I have one 2008 DC at a secondary site.
    The 2003 domain controller is also running Exchange 2007.  We have a new server running Exchange 2010 but we have kept that old 2007 running because it does call recording and we have not been able to migrate that off yet.
    A consulting company told me not to DCPROMO the 2003 server down until we were able to remove Exchange 2007.  
    I want to DCPROMO down the 2003 server and raise the domain function level but was a little nervous after they told me that.
    However, I can't really understand why Exchange would make a difference whether the server is a domain controller.  Really Exchange should have never been put on a domain controller anyway.
    One more thing, the 2003 server is also the DHCP server, have not migrated that yet either.
    Any thoughts/tips?  
    Thanks,

    Hi,
    Installing Exchange on a domain controller is not recommended, if we have install Exchange on DC, and then change DC to member server may lose functionality in Exchange, here is an article talked about Exchange Server 2003 and Domain Controllers, it
    should also apply for Exchange 2007, please go through it:
    http://theessentialexchange.com/blogs/michael/archive/2007/11/13/exchange-server-2003-and-domain-controllers-a-summary.aspx
    Regards,
    Yan Li
    Regards, Yan Li

  • Windows 2003 to windows 2008 r2 migration-non dc

    Hello, 
    Am wondering how can we migrate NON DC windows 2003/2003r2 to windows 2008/2008r2 ?
    Below links explains how to do migration or prerequisites but is anyone already done this project?
    https://technet.microsoft.com/en-us/library/cc755199(v=ws.10).aspx
    Also i have found another blog about about migration windows 2003 to windows 2008, but ""IS IT ONLY FOR DC or APPLIES TO NON DC AS WELL""?
    http://blog.pluralsight.com/upgrading-to-server-2008-from-server-2003
    regards,
    Dharanesh,

    Hello,
    if the installed software is checked to work with the new OS version you can use the installation disk from the new OS version, if the architecture(32bit or 64bit could be ONLY upgraded to the same) is the same, and do an in place upgrade.
    Also keep in mind that you have to check for drivers BEFORE starting.
    Best regards
    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://blogs.msmvps.com/MWeber
    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
    Twitter:  

  • Best way to migrate SharePoint 2003 data into SQL Server 2008

    Hi Experts,
        I am planning to migrate data from SharePoint 2003 into SQL Server 2008. After the migration SharePoint site will be deleted in couple of months and then that data will be feed into .Net Front end application
    1) What is the best and easy way to do it?
    2) Is there any way to automate the migration process? i.e. If a new record gets entered into SharePoint it should be populated into SQL Server 2008.
    3) Any other suggestions
    Thanks,
    John

    Dear John,
                    If it's just a few lists, and you just want to import them "as-is" then it should be possible to do so ... and survive to tell the about it ;-)
                   Generally speaking, You will need to write a small process (program or script) to read/parse each list and check if the item(s) are in the target table (I assuming that there is a distinct table as target
    for each list, and that each list has 'something" you can use to distinct each row), if it's not there, the just add them according to your needs.  
                   Then just rerun the process periodically and it would keep your databases up to date (you could even set ti up to update those records that have changes, but that would delay your process significantly)
                    What i just described is doable, and not TOO complicated, it could be done i a lot different ways, and with different alternatives of programming/scripting languages. for sure you can do it in any flavor
    of .net language, and even powershell.
                    As I mentioned, this is speaking in general, the actual implementation would depend on your specific needs and the kind of data that you have/need to keep.
    Best Regards / Saludos, Marianok
    Disclaimer: This post, and all included code and information is provided "AS IS" with no warranties or guarantees and confers no rights. Try it at your own risk, I take no responsibilities.
    Aclaración: Esta publicación, y todo en código e información en la misma, es provista "AS IS" / "Como Está" sin garantía alguna y no le confiere ningún derecho. Pruebelo su propio riesgo. No asumo responsabilidad alguna.

  • 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

  • Migrate MOSS 2007 Server from Server 2003 (32-bit) to Server 2008

    I have a client with MOSS 2007 installed on Windows Server 2003, and a database server (SQL 2005) also on Server 2003. they have two new Windows Server 2008 servers, and they wish to do a migration.  They have custom Features, including Event Receivers
    installed in their environment.
    Do I need to install the 32-bit edition of MOSS 2007 on the new server in order to be able to use the pre-compiled custom Features used in the current server?
    My plan is to do the following:
    (a)  Migrate databases from current database server (SQL 2005) to new database server (SQL 2008),
    (b)  Re-assign SQL redirection to new database server (the database was previously on the same box as the WFE, and this was separated out last year to another server, but redirecting the SQL Server,
    (c)  Install MOSS 2007 (32-bit) on the other new server
    (d)  Patch both instances of MOSS 2007 to the same point
    (e)  Create (dummy) site collection on new server, and install all custom Features on server
    (f)  Add new server to existing Farm
    (g)  Remove previous server from Farm
    What must I do to install existing custom Features on new server?
    Is there anything that I have left out of the process?  Do I need to do anything about the SSP running on the current server?

    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"

  • 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

  • Migrating DC's from Server 2003 to Server 2008 Enterprise R2

    I am in the process of testing a migration of our DC's to 2008 R2. 
    I've read countless articles, step by steps, etc, but am still having trouble deciding the best way to figure this thing out. Hoping that someone can give me some pointers on what might be the best way to do this. It should be fairly straightforward but
    I am just unsure of how the fact that the two DC's being on different networks & the DFS will play in to things. 
    I currently have 
    (1) PDC residing in a colo (172.16.36.x) Server 2003
    (1) Mail server residing in a colo (172.16.36.x) Server 2008
    (1) DC residing in our office (172.16.35.x) Server 2003
    These 2 different networks are connected by VPN from our office to the colo. 
    The DC in the office is running DHCP and DNS. It also acts as the File Server. The data is then being replicated using DFS from the office DC to the colo PDC. 
    We have purchased 2 new servers (physical) to replace the DC and PDC and also am installing Server 2008 R2. 
    From what I've gathered, I should join these new machines to the domain and begin migrating. 
    Step 1: Install Active Directory on new Servers, Install/Migrate DNS?
    Step 2: Transfer Roles (Looking for recommendation as to which DC acts for which Role also, or should the PDC hold all roles?) 
    Step 3: Migrate files/shares and set up DFSR? 
    If anyone can offer some advice on how to make this as simple as possible I would greatly appreciate it! 

    Thanks for the link. I've been able to successfully migrate almost everything over, just had a few questions about DFSR. 
    This is the scenario: 
    Server A (old file server, located in office)
    Server B (old file server, located in colo)
    Server C (new file server, located in office)
    Sever D (new file server, located in office) 
    I have 2 servers currently. Both running Server 2003 (DFS) acting as file servers. Server A is the preferred connection when using DFS, so typically any changes from users will be made on Server A and then replicated to Server B.  I've tested the File
    Server Migration Toolkit to migrate files/shares over from server B to Server D, it seems to work fine. Now, I am not sure what the best way to migrate everything would be. 
    This was my thought process but I am not certain this is the best way/or will work as intended.
    Use FSMT to copy all shares from Server A to Server C. 
    Plan for short downtime to copy all open files from Server A to Server C. 
    Map users to shares on Server C. 
    Begin replication from Server C to Server D. When complete map users to DFSR link. 
    Then take Server A and B offline. 
    Something I wasn't sure about is maybe using FMST to migrate things from Server B to Server D. Would it then compare to Server C through DFSR or does this replication have to occur "naturally"? 
    Something else I am a little confused about is when does DFSR start being used? Do the old servers have to be offline first? 

  • Migrating Windows Server 2003 File Cluster to Windows Server 2008 R2

    Hello,
    I have a very large Windows Server 2003 2 node file cluster that I would like to upgrade to Windows 2008 R2. I need to do this inplace (same server hardware) and I would like to use the existing storage if possible (I could buy more if it would make things
    easier).
    Is there a step by step guide that can tell me how to do this upgrade inplace or can anyone give me details on how to do this? I've looked at a few articles and they are not very descriptive on what to do.

    What Microsoft calls an inplace upgrade is option 2 below
    There are two basic migration/upgrade methods for a 2003 cluster to 2008
    1) Build on new hardware, and move the disk/migrate the data. 
    2) Break cluster and remove one node, use that node to build a new one node cluster.  Repeat by removing nodes and adding to new cluster.
    Here is the MS Step-by-step guide for both of these approaches.
    http://technet.microsoft.com/en-us/library/cc754481(WS.10).aspx

  • Problems after print server migration to Windows Server 2008 R2

    Hi all,
    New forum member, first time poster. I am at my wits end and have concussion from banging my head on the desk for several days running. Hopefully someone here may be able to help.
    Environment
    I have recently moved our printing environment from a Windows Server 2003 machine to a new Server 2008 R2 machine in prep for rolling out Windows 7 x64 clients. We have 30-40 printers, majority of which are HP's (M2727's, P4015dn's, CM3530's, P2035's & a CM8060).
    My procedure for setting up the printers on the new server involved manually creating each printer and using up-to-date drivers, we wanted to start fresh. The HP's are all using the HP Universal PCL 5 or PCL 6 (61.115.1.10527) x86 & x64 driver. We use Desktop Authority on logon to install the required printers for each client.
    Problems
    Since everyone is now running through the 2008 R2 server we have had a bunch of intermittent problems pop up all over the place, mostly with our HP printers. When using the PCL6 driver some applications print a page or 10 of garbled gibberish (wingdings etc), so most printers are now using the PCL5 driver. Other applications print the error "PCL XL error" when using PCL6. Sometimes reinstalling the printer on the client machine will resolve these errors, however they tend to resurface.
    When we use the PCL5 driver our M2727's intermittently report "Out Of Memory" on the printer display (they are stock with 64M RAM each) - upgrading the RAM may fix this but we never had this problem before on the 2003 server. This problem is not specific to the size of the printed document - it could be a 20 page report or a 2 page excel document. Resetting the printer will generally clear this issue temporarily. This is currently our most annoying/biggest issue.
    Some people are having issues printing to a FujiXerox 340A-AP printer - in particular 1 person is able to print fine, where as another prints and the print margin appears to be far too small. After confirming all print margins on the server then reinstalling the printer on the client machine, the problem still persists. We have two FujiXerox printers, the second one is working as intended for 8-10 users with the exact same settings.
    Attempted Fixes
    These are some of the attempted fixes that I have tried:
    Turning it off and on
    Upgrading the firmware on the M2727's to resolve garbled printing & out of memory
    Upgrading the firmware on the CM3530's to resolve garbled printing
    Reinstalling all HP Universal PCL5/PCL6 x86 & x64 drivers on the print server
    Ensuring that the 2008 R2 server is 100% up-to-date with MS patches
    Backing up all printers on print server, removing the print server role, deleting all printers & drivers, rebooting, reinstalling the print server role and restoring all printers from backup
    Upgraded Desktop Authority to the latest version - as this application is in charge of installing the printers on logon
    As you can see we are having a lot of problems and nothing seems to make any sense. None of this happened before Windows Server 2008 R2 was brought in to the equation.
    If anyone is able to provide any assistance that would be greatly appreciated.
    Many thanks,
    Hartz.
    tldr; our printers are screwed since migrating to Windows Server 2008 R2.

    Hi all,
    New forum member, first time poster. I am at my wits end and have concussion from banging my head on the desk for several days running. Hopefully someone here may be able to help.
    Environment
    I have recently moved our printing environment from a Windows Server 2003 machine to a new Server 2008 R2 machine in prep for rolling out Windows 7 x64 clients. We have 30-40 printers, majority of which are HP's (M2727's, P4015dn's, CM3530's, P2035's & a CM8060).
    My procedure for setting up the printers on the new server involved manually creating each printer and using up-to-date drivers, we wanted to start fresh. The HP's are all using the HP Universal PCL 5 or PCL 6 (61.115.1.10527) x86 & x64 driver. We use Desktop Authority on logon to install the required printers for each client.
    Problems
    Since everyone is now running through the 2008 R2 server we have had a bunch of intermittent problems pop up all over the place, mostly with our HP printers. When using the PCL6 driver some applications print a page or 10 of garbled gibberish (wingdings etc), so most printers are now using the PCL5 driver. Other applications print the error "PCL XL error" when using PCL6. Sometimes reinstalling the printer on the client machine will resolve these errors, however they tend to resurface.
    When we use the PCL5 driver our M2727's intermittently report "Out Of Memory" on the printer display (they are stock with 64M RAM each) - upgrading the RAM may fix this but we never had this problem before on the 2003 server. This problem is not specific to the size of the printed document - it could be a 20 page report or a 2 page excel document. Resetting the printer will generally clear this issue temporarily. This is currently our most annoying/biggest issue.
    Some people are having issues printing to a FujiXerox 340A-AP printer - in particular 1 person is able to print fine, where as another prints and the print margin appears to be far too small. After confirming all print margins on the server then reinstalling the printer on the client machine, the problem still persists. We have two FujiXerox printers, the second one is working as intended for 8-10 users with the exact same settings.
    Attempted Fixes
    These are some of the attempted fixes that I have tried:
    Turning it off and on
    Upgrading the firmware on the M2727's to resolve garbled printing & out of memory
    Upgrading the firmware on the CM3530's to resolve garbled printing
    Reinstalling all HP Universal PCL5/PCL6 x86 & x64 drivers on the print server
    Ensuring that the 2008 R2 server is 100% up-to-date with MS patches
    Backing up all printers on print server, removing the print server role, deleting all printers & drivers, rebooting, reinstalling the print server role and restoring all printers from backup
    Upgraded Desktop Authority to the latest version - as this application is in charge of installing the printers on logon
    As you can see we are having a lot of problems and nothing seems to make any sense. None of this happened before Windows Server 2008 R2 was brought in to the equation.
    If anyone is able to provide any assistance that would be greatly appreciated.
    Many thanks,
    Hartz.
    tldr; our printers are screwed since migrating to Windows Server 2008 R2.

  • Windows server 2008 R2 x64 Authentication failure while try to access Windows server 2003 R2

    Hello,
    I try to access Windows Server 2003 R2 Standard from Windows Server 2008 R2 x64 standard using integrated windows authentication . And because my application tries to read SQL server i'm getting and error that user is not trusted. Then I tried to open a
    simple shared folder on  2003 and none of the users is able to do it. Both servers are part of common workgroup in the same IP range. Using domain is not an option. Migrating 2003 to 2008 is not an option either. The specific DB provider I have to use
    supports only windows authentication, so creating user into SQL server is not an option too. I have tested many applications and cases which requires/uses windows authentication and non of the manage to connect.
    Any help is very welcome because things are urgent!
    Authentication failure

    That method in workgroup mode may be a problem.
    Authentication in SQL Server
    Might ask them over here.
    SQL Server forums on
    MSDN
    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]
    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Maybe you are looking for