Is Windows 2003 member servers still able to authenticate against Windows Server 2012 R2 AD after mirgation?

Hi,
We are planning to migrate Windows Server 2008 R2 AD to Windows Server 2012 R2 AD. But we have some Windows 2003 member servers (Running RADIUS for VPN user to authenticate their AD accounts). Does anyone know that existing Windows 2003 member
servers still able to authenticate on Windows Server 2012 R2 AD after migration and function properly? Just wanted to make sure Windows Server 2012 AD support Windows 2003 member server.
Thanks.
M

Hi,
Thanks for your post.
Is there any Windows server 2003 domain controller in your domian?
If yes, i think you could refer to this article:
http://blogs.technet.com/b/askds/archive/2014/07/23/it-turns-out-that-weird-things-can-happen-when-you-mix-windows-server-2003-and-windows-server-2012-r2-domain-controllers.aspx
Regards.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Similar Messages

Windows 2003 SP2 servers migrating from IIS 6.0 to IIS 7.5 without upgrading to Windows 2008 R2

I have 3 Windows 2003 SP2 servers running IIS 6.0 and my client wants to upgrade to IIS 7.5 without having to upgrade the OS to Windows 2008 R2. Is this possible?
Thanks

No I'm afraid not. The full versions of IIS depend on the OS, so IIS6 on 2003, IIS7 on 2008, IIS7.5 on 2008 R2.
The Express version of IIS can be installed on 2003 but that's for developers only so no use in your situation.
Also worth nothing in terms of upgrading, unless your 2003 installation is 64-bit then you can only do an in place upgrade to 2008 IIS7. There's no 32-bit option with 2008 R2, and no way to do an in place upgrade between 32-bit and 64-bit, so if you really
need to upgrade to IIS 7.5 then your only option would be to start with a new install and then migrate the websites from one server to another.

If I Factory Reset My PC "AFTER A YEAR" of Windows 10 Released, I Still Able Upgrade to Windows 10?

HELP~!!!I currently running on Windows 8.1. If I upgrade to Windows 10 "now" and factory reset my pc "after one year" of Windows 10 released, (that means Windows will go back to Windows 8.1??)Am I still able to upgrade to Windows 10 that time? Thank you.

My understanding is the free upgrade is good for 1 year meaning July 29,2016, it no longer exists. So you won't be able to upgrade for free after that date. When you upgrade I believe there's a choice to keep your old Windows version so you can go back to it (8.1 or whatever it is).

Laptop Bios cannot detect new HDD but still able to boot into windows

I have a Pavilion Dv5 1010tu which the original HDD have died. So i bought a new Samsung 320GB Sata and install Windows 7 on it. After Windows installation finished successful, I manually restart the laptop without Windows setup disk and it stop at dos screen with the error message :
Boot device not found.
Please install an operating system on your hard disk.
Hard disk (3F0) ...
I check bios and it didn't show any hard drive but when i re-insert Windows setup disk and restart, it can boot in windows without any problem. How can i fix this issue? I already update Bios and run hard disk self test though Bios setup without failed but it still not recognize HDD
Edit: My original HDD was Hitachi 250GB Sata
Bios version F.21A

~if advanced mode is off turn it on~ It sound easy huh. I would like to ask How can I access to advanced mode in Bios of Hp laptop? It's impossible.
defective drive ??? It a newly purchased HDD and it run perfectly fine, i'm posting this message using the laptop i mention above with this HDD as the only hard drive and installed with Windows 7
Any other idea/ help will be very appreciated , please

Data Integrator 11.7.x and VM WIndows 2003/2008 Servers

Is Data Integrator 11.7.x supported in the following platform -
VM Windows 2003 Server
VM Windows 2008 Server
??? Thanks

The first one yes, for the latter you need to upgrade to DI 12.2 ( DataServices 3.2)

Windows 2003 R2 Gray Screen Hang on HP DL380 G5 when restarting or shutdown after Nov/Dec 2011 Windows Update

I’ve 4 identical HP DL 380 G5 Servers with Windows 2003 R2 Std. The 4 machines have the same Windows driver version and motherboard BIOS version. 2 have no problem. 2 have problems after Nov/Dec 2011 Windows Update!
After running for a few days from power-up, the 2 problem servers will hang at gray screen during restart. After clicking for restart,
- The Event Log service will stop normally so there is no more error log can be seen!
- The IP ping to the server can still work. The mouse pointer in Windows can still be moved.
- The Windows shutdown gray screen can be shown.
- [Ctrl-Alt-Del] has stopped to function.
Then the system just freezes at that status. I can only cold-boot the system!
After power-up again, I can do the Windows restart / shutdown normally! But after a few day of running, the above symptom repeats! The symptom happened since I installed the Windows Update in Dec 2011. It didn’t happen before that!
Anyone can give a hint on how to diagnose it?

Hi,
In order to troubleshoot the server hang issue, you can first preform a clean boot on the problematic system.
Steps:
====================
1. Click Start->Run…->type
msconfig and press Enter
2. Click Services tab and select Hide All Microsoft Services
and Disable All third party Services
3. Click Startup tab and Disable All startup items
4. Click OK and choose Restart
5. After reboot, check whether the problem still occurs
If the server hang on issue still continues in clean boot mode, for the further troubleshooting, you may check in the Task Manager to see which process takes the memory resources.
Meanwhile, you can also use reliability and performance Monitor to track down what cause the performance issue.
Windows Reliability and Performance Monitor
http://technet.microsoft.com/en-us/library/cc755081(WS.10).aspx
Windows Performance Monitor
http://technet.microsoft.com/en-us/library/cc749249.aspx
Best Regards,
Aiden
Aiden Cao
TechNet Community Support

Temporary wim-files for multicast transmissions still needed for WDS installation in Server 2012 R2?

Acording to
https://technet.microsoft.com/en-us/library/dn281955.aspx one of the new features for WDS in Server 2012 R2 for multicast is:
Improved multicast deployment by eliminating the need for making a local copy of the install.wim file. You can apply the install.wim file while it is being downloaded without significant impact to the application process.
However, this doesn't seem to be activated by default and I still get the following error when installing one or more machines using multicast:
"Windows Setup cannot locate a valid hard drive to store temporary installation files." However, once I remove Multicast from this install image, it installs without any problems at all.
I have also noticed that while multicasting, the installation will use the "Copying Windows files" phase, while downloading and copying the install.wim (or whatever name it is) locally on the hard drive first, so this will require lots of space.
So the question is, how do you enable this new feature that should be a part of WDS in Server 2012 R2???

Full version:
Following steps could help enable the feature:
1. Mount the boot image using dism.
e.g.
>dism /mount-wim /wimfile:c:\remoteinstall\boot\x64\images\boot.wim /index:2 /mountdir:c:\mount
2. Create a metadata file if no existing one. The metadata file should be in mountdir from the first step under mountdir\sources. And the file name should be: WdsClientMetadata.txt
3. Add entry to the metadata file: WDS.Client.Multicast.WIM.Streaming.Enabled=true
4. Save changes and unmount the boot image
e.g.
>dism /unmounts-wim /mountdir:c:\mount /commit
Sorry for the late reply, but I had to test this thoroughly since I didn't get it working right away. I tried both the regedit you first mentioned, and later also creating a textfile in the "/index:2 boot.wim", both without any success. I noticed
that creating the sources\WdsClientMetadata.txt with the data "WDS.Client.Multicast.WIM.Streaming.Enabled=true" gives me an error upon booting into WDS as follows (EUFI/IPv6-boot):
Same happens if I boot using IPv4 (an non-UEFI boot), except that there would be a plain IPv4-address instead in the error msg. Just for troubleshooting I tried writing WDS.Client.Multicast.WIM.Streaming.Enabled=false in the file instead, and WDS would throw
me the exact same error message. Once I delete the file sources\WdsClientMetadata.txt from the WDS/Boot image, the client boots ok, both for IPv4/IPv6. Disabling the firewall on the WDS didn't help, so something in the configuration is still missing? I'm getting
to a dead end here, and I suppose you're all out of advice on this one?
Thank you Shaon Shan for your great effort so far.

Still cannot install the agent on Server 2012 R2 Core

Hi
I'm using the latest build of the agent (that I could find - 2.0.8692).
This KB http://support2.microsoft.com/kb/2997692/en-us says that 2.0.8689 and above should be supported on Windows Server 2012 R2 Core.
The installation works, but when I'm about to do the postsetup (Register Server Wizard) I get an unhandeld exception and cannot continue.
The error reads:
Creating an instance of the COM Component with CLSID {DC1C5A9C-E88A-4DDE-A5A1-60F82A20AEF7} from the IClassFactory failed due to the following error: 80040111 ClassFactory cannot supply requested class (Exception from HRESULT: 0x80040111 (CLASS_E_CLASSNOTAVAILABLE))

I am getting the same error, Hyper-V Server 2012R2
Full error
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Runtime.InteropServices.COMException (0x80040111): Creating an instance of the COM component with CLSID {DC1C5A9C-E88A-4DDE-A5A1-60F82A20AEF7} from the IClassFactory failed due to the following error: 80040111 ClassFactory cannot supply requested class
(Exception from HRESULT: 0x80040111 (CLASS_E_CLASSNOTAVAILABLE)).
   at System.Windows.Forms.OpenFileDialog.CreateVistaDialog()
   at System.Windows.Forms.FileDialog.RunDialogVista(IntPtr hWndOwner)
   at System.Windows.Forms.CommonDialog.ShowDialog(IWin32Window owner)
   at Microsoft.Internal.CloudBackup.UI.Wizards.Activation.VaultCredentialBrowsePage.vaultCredentialBrowseButton_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.34014 built by: FX45W81RTMGDR
    CodeBase:
file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
PostSetup
    Assembly Version: 1.0.523.0
    Win32 Version: 2.0.8692.0
    CodeBase:
file:///C:/Program%20Files/Microsoft%20Azure%20Recovery%20Services%20Agent/bin/PostSetup.exe
TraceWrapper
    Assembly Version: 1.0.523.0
    Win32 Version: 2.0.8692.0
    CodeBase:
file:///C:/Program%20Files/Microsoft%20Azure%20Recovery%20Services%20Agent/bin/TraceWrapper.DLL
CBEngineServiceProxy
    Assembly Version: 1.0.523.0
    Win32 Version: 2.0.8692.0
    CodeBase:
file:///C:/Program%20Files/Microsoft%20Azure%20Recovery%20Services%20Agent/bin/CBEngineServiceProxy.DLL
System.Runtime.Serialization
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.34230 built by: FX452RTMGDR
    CodeBase:
file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.34239 built by: FX452RTMGDR
    CodeBase:
file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
    CodeBase:
file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
    CodeBase:
file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
CBActivationWizard
    Assembly Version: 1.0.523.0
    Win32 Version: 2.0.8692.0
    CodeBase:
file:///C:/Program%20Files/Microsoft%20Azure%20Recovery%20Services%20Agent/bin/CBActivationWizard.DLL
CBWizFx
    Assembly Version: 1.0.523.0
    Win32 Version: 2.0.8692.0
    CodeBase:
file:///C:/Program%20Files/Microsoft%20Azure%20Recovery%20Services%20Agent/bin/CBWizFx.DLL
CBClientCommon
    Assembly Version: 1.0.523.0
    Win32 Version: 2.0.8692.0
    CodeBase:
file:///C:/Program%20Files/Microsoft%20Azure%20Recovery%20Services%20Agent/bin/CBClientCommon.DLL
System.ServiceModel
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.34230 built by: FX452RTMGDR
    CodeBase:
file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.ServiceModel/v4.0_4.0.0.0__b77a5c561934e089/System.ServiceModel.dll
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
    CodeBase:
file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
CloudUtils
    Assembly Version: 1.0.523.0
    Win32 Version: 2.0.8692.0
    CodeBase:
file:///C:/Program%20Files/Microsoft%20Azure%20Recovery%20Services%20Agent/bin/CloudUtils.DLL
System.ServiceProcess
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
    CodeBase:
file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.ServiceProcess/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll
NativeMethods
    Assembly Version: 1.0.523.0
    Win32 Version: 2.0.8692.0
    CodeBase:
file:///C:/Program%20Files/Microsoft%20Azure%20Recovery%20Services%20Agent/bin/NativeMethods.DLL
SMDiagnostics
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.34230 built by: FX452RTMGDR
    CodeBase:
file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/SMDiagnostics/v4.0_4.0.0.0__b77a5c561934e089/SMDiagnostics.dll
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.34230 built by: FX452RTMGDR
    CodeBase:
file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
System.ServiceModel.Internals
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.34230 built by: FX452RTMGDR
    CodeBase:
file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.ServiceModel.Internals/v4.0_4.0.0.0__31bf3856ad364e35/System.ServiceModel.Internals.dll
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
    CodeBase:
file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
System.IdentityModel
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.34230 built by: FX452RTMGDR
    CodeBase:
file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.IdentityModel/v4.0_4.0.0.0__b77a5c561934e089/System.IdentityModel.dll
CBCommonControls
    Assembly Version: 1.0.523.0
    Win32 Version: 2.0.8692.0
    CodeBase:
file:///C:/Program%20Files/Microsoft%20Azure%20Recovery%20Services%20Agent/bin/CBCommonControls.DLL
CBUIErrorHandling
    Assembly Version: 1.0.523.0
    Win32 Version: 2.0.8692.0
    CodeBase:
file:///C:/Program%20Files/Microsoft%20Azure%20Recovery%20Services%20Agent/bin/CBUIErrorHandling.DLL
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Authenticate against windows 2000 server securtiy using Java.JNI

How could you use Java or JNI to read the password and group membeship from the operating system for a given windows 2000 user, from a servlet/class?

Are you looking to build some sort of single sign-on module? You wouldn't be able to get the password, but you might be able to pass a token indicating the users credentials. You'd have to delve into the MSDN resources to get that.
Once you figure out how to what you want using COM, you can more easily integrate it into Java using the sourceforge projects Jacob or JAWIN.

Anyone able to authenticate against password protected Samba/SMB shares?

With on 10.5.8, I was able to connect to my Linux server using the Samba protocol. When the Samba shares did not allow guest/anonymous logins, I was able to supply an user/password, and it worked wonderfully.
Currently, on 10.6, I'm able to mount shares with guest/anonymous access but I am not able to mount password protected shares.
In the past, there was a problem in the smb.conf setting of:
encrypt password = yes
And I've tried both "yes" and "no" values to no avail. Has something broke or changed in the way 10.6 talks Samba?
Message was edited by: rthien

Hi all,
I found the answer on my side. But it is rather strange that it worked with 10.5.8 and older. But it does not work with 10.6.
In Linux, in my smb.conf file, I had:
security = SHARE
If I change it to:
security = USER
and add the line:
user = +comma separated list of users+
To effect this new settings, I had to restart the Samba daemons. And then things started to work for me.

Moving printers to consolidate servers without interrupting users [Windows 2003 to 2003]

Greetings!
How do I go about moving network printers served from ServerA to ServerB, decommission/shutdown ServerA, and be completely transparent to users without causing them the need to remap printers?
My company is still at Active Directory level Windows 2003 SP2, and has all of our printers on several Windows 2003 SP2 servers. I am in the midst to decommission several old servers and consolidate print servers and then upgrade the domain to Server 2012
levels.
Right now, a user may have a network printer setup so that it is listed as "Printer1 on ServerA"
I want it so that when I move the printers to ServerB, users can still use their already setup "Printer1 on ServerA", instead of having to map them with "Printer1 on ServerB". Although, any new printers added from the consolidation point
forward to a users PC would be "Printer1 on ServerB".
My plan is to use my Windows 7 PC to:
Use Print Management to migrate/export ServerA printers to a file.
Use Print Management to migrate/import that ServerA printers file into ServerB. Using "Keep existing printers" in Import mode and "List All Printers" for List in the directory. [That would add ServerA's printers to
ServerB while keeping ServerB's printers. But I'm a little unclear which option to use for List in the directory.]
Shut down ServerA.
In our AD DNS, delete ServerA's A record and then either (a) add an A record for ServerA using ServerB's IP address, or (b) add a CN record for ServerA to point to ServerB's FQDN. [I think (a) is the better option, right?]
And then after the DNS refresh, the jobs should just come out of Printer1 on ServerA (as already listed/setup on my workstation) even though Printer1 now resides on ServerB.
I tried that plan last night, and things just didn't quite work out. My workstation said Printer1 on ServerA was Offline and I couldn't print to Printer1 on ServerA (which was imported onto ServerB) even though my DNS had ServerA with ServerB's IP.
For now I brought ServerA back online and people are working.
What am I missing or should be doing differently? Any issue with local security that would prevent one server to not accept commands directed to another servername? Thanks for your input!
Visual nutshell:
Printer1/ServerA ---> shutdown ServerA ---> Printer1/ServerB while those with Printer1/ServerA definitions on their workstations would still print.

When I last went from 2003 to 2008 R2, I did things a bit different. I brought up the new server and migrated all printers. I then had both servers running at the same time with the same configuration but all the clients
were pointing to the old server. To move the clients I deployed this vbs script to all users using group policy as a logon script:
http://gallery.technet.microsoft.com/scriptcenter/20428e3a-12c6-4354-bddf-d748367fca72#content. I left both servers running for some
time until all users were redirected. I frequently then checked the old servers event logs for any print jobs until I no longer saw any and then shutdown the old server. Hope that makes sense.
+1, I kinda do it that way too. (except I didnt know that script, as I used GPP to erase all printer connected & I was re-doing the printer connection after with GPP too)
Regards, Philippe
Don't forget to mark as answer or vote as helpful to help identify good information. ( linkedin endorsement never hurt too :o) )
Answer an interesting question ? Create a
wiki article about it!

Moving member servers without DC

Hi
I have recently been asked to move some server's (running windows server 200 and windows server 2003 r2) to a new site as the old site is being decommisioned, the DC's will be decomm'd, as the legacy data will only be required for reference purposes and
the business is closing down, as the company is being closed down.
The DC's run DNS, DHCP and ADDS.
The servers that will be moved are purely application servers, I was wondering what would happen when the DC's are powered off? Will the member servers still function and communicate, also the time server is one of the DC's, how will this affect the retrieval
of data from the member servers.
Thanks
Gin

The servers that will be moved are purely application servers, I was wondering what would happen
when the DC's are powered off?
If I understand well, the DCs will be decommissioned and the domain will no longer exist. If this is the case then you will need to disjoin these servers from the domain to avoid false positive alerts in the logs and so that you can do the things in the
correct way.
About the impacts on your application servers, you need to know their dependencies and relation with AD. If you have an AD based application then it will no longer work. You need to check each of these applications and do the assessment of the impacts. A
test environment would help and contacting the application developers / support would be helpful too.
Will the member servers still function and communicate, also the time server is one of the DC's,
how will this affect the retrieval of data from the member servers.
About which data are you speaking? You need to check the requirements for your applications.
As for the time sync, you need to think about hosting an internal NTP server that is in sync with external ones or simply make all your servers point to external NTP servers for time sync as you will no longer have DCs.
The servers will hold data and the legacy application, without the DC's will the servers boot up
and be able to talk to each other, also what happens with the time synchronisation when there's no DC available.
They will be able to boot and use the cached credentials for authentication. For the time sync, it will no longer work as your DCs will be no longer available.
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

Need to decommission a Windows 2003 server....

I have a Windows 2003 DC with all the FSMO roles. It was the first DC of the domain
I also have 3 other DCs that are Windows 2008 R2.
All of the DCs are global catalogs.
DHCP Server is running on the Windows 2003 DC.
All of the DCs run DNS Server but a majority of the PCs in the network point to the Windows 2003 DC for DNS resolution.
1) What do I need to do to get rid of the Windows 2003 DC cleanly and efficiently? Is there a certain order of steps?
2) How should I split the FSMO roles between the remaining 3 Windows 2008 R2 DCs?
3) I want to split the DHCP between the 3 DCs. Should I copy the DHCP database from the Windows 2003 DC and import it? Or should I recreate 3 non-overlapping scopes?

To migrate the FSMO roles have a look at this guide
http://support.microsoft.com/kb/324801 which explains all the steps. Once everything's been moved you can demote the server so it's no longer a DC, though personally I'd opt for shutting it down where possible initially, just so it's still there
if you find something hasn't been moved. Once you're happy everything is still working without it being there then make sure you demote it, otherwise you'll end up with old records hanging around. If you want to make absolutely sure you could have a look at
http://msmvps.com/blogs/acefekay/archive/2010/10/05/complete-step-by-step-to-remove-an-orphaned-domain-controller.aspx which details the steps required if a server isn't cleanly removed and you end up with orphaned records.
Not sure about the splitting of the FSMO roles to be honest. I suspect realistically your best off keeping them all on the one server, since it will make management a lot easier (eg you know which one server is more important than the others), and of course
if you split it then rather than having a 1 in 3 chance if one of the servers died of having to recover that info, you'd now be guaranteed problems regardless of which server died.
For DHCP there's a guide here for how
http://blogs.technet.com/b/networking/archive/2008/06/27/steps-to-move-a-dhcp-database-from-a-windows-server-2003-or-2008-to-another-windows-server-2008-machine.aspx for how to move DHCP to another server. In terms of multiple servers, unless you want to
go for a full on DHCP failover setup, splitting the scope is the best option, since you can't have multiple DHCP servers actively giving out the same IPs. I haven't tried it to be honest, but since the scope it only a part of the DHCP settings, I'd suggest
you should be able to use the above process, import those settings to each DHCP server, and then once imported edit the DHCP scope on each such that they no longer overlap. That way you ensure that all the other settings remain the same and are completely
identical.

Windows 2003 Server Domain Login issues

We have installed Windows 2008 R2 Servers in our existing environment which was running on Windows 2003 R2. I have configured Windows 2008 as DNS and Global Catalog Server, transferred all the FSMO roles to new Server and tested all the clients were
able to logon to the Domain controller with not issues. Added one more Windows 2008 R2 Server as and ADC before completing demoting the Windows 2003 R2 Domain controller. For a test phase I have shutdown the Windows 2003 R2 DC and noticed that
few of the member Servers running Windows 2003 OS are not login to Domain whereas Windows 2008 Member Servers, Windows XP, 7 and 8 machines are able to login to domain. Once I bring up the Windows 2003 R2 DC those machines are able to login to the Domain.

Hi shujathmsa,
à
For a test phase I have shutdown the Windows 2003 R2 DC and noticed that few of the member Servers running Windows 2003 OS are not login to Domain
Based on your description, it seems that this issue just occurred in Windows Server 2003. Would you please
let me know the complete error message that you can get when join Windows Server 2003 to the domain?
Meanwhile, please follow the path:
C:\Windows\debug folder and check NetSetup.LOG file if find some relevant clues.
If any update, please feel free to let us know.
Hope this helps.
Best regards,
Justin Gu

N1 SPS 6.0 Installation problem on windows 2003

Hello,
I have tried to install N1 SPS 6.0 on windows 2003. I was able to finish installlation successfully. But When I try to access tool from http://localhost:8080 , It is not working. I am new to tool , I am installing first time so not able to figure out. I have checked the service for master server is starting under windows services. What else do I need to check? Are there any prerequisite to install N1 SPS 6.0 Master Server on windows?
Thanks. Any help will be appreciated.
Thanks
Bhavika

1. While installation did you configured http or https for UI ? I configured http
2. If https, did you provided the keystore file as part of installation or not? No
3. If https and opted to provide the keystore file after the installation? No
4. if you run 'netstat -an | more' can you find port 8080 in the list? I cannot see
5. are you finding any error messages in {install-dir}\server\bin\cr_server.out file? if so, can you share that error message
I cannot see cr_server.out file under C:\Program Files\N1 Service Provisioning System\6.0\server\bin that is my install directory
6. Related to N1 SPS, are you finding any errors in windows event log? if so, can you share the error message
7. From DOS command prompt, when you run "net start crserver60" or "net start postmaster60" or "net start crprepdb60" are you getting the following error? *
The requested service has already been started.
I see following message
C:\Documents and Settings\Administrator>net start crserver60
The N1 Service Provisioning System 6.0 Server service is starting.
The N1 Service Provisioning System 6.0 Server service was started successfully.
8. Do you have the local user postgres in your system What do u mean by local user ? I have installed postgres on my system with postgres user.
9. instead of using "http://localhost:8080", if you try to access the UI admin through "http://{windows-host-name}:8080", does it work? * I tried both way , it does not work *

Is Windows 2003 member servers still able to authenticate against Windows Server 2012 R2 AD after mirgation?

Similar Messages

Maybe you are looking for