Windows Essentials 2012 and XP-based clients

[Mick]

I recently swapped out a past-it SBS 2003 server for a Windows Essentials 2012 replacement. I demoted the old server from domain controller status and I had hoped to be able to use the old server as a back-up/storage device over the LAN, but I'm unable to join it to the domain using W2012's wizards. I understand that this is because SBS 2003 is essentially a jumped-up Win XP, and W2012 doesn't support XP clients. I've tried joining it to the domain manually - and it is reporting that this succeeded - but the new W2012 server still won't 'see' it (and vice-versa).

I'm wondering if my original plan to use this old box as a storage device just isn't going to work, but thought I'd ask here just in case anyone has run into this or a similar scenario and if so, if they managed a solution.

Many thanks in advance for any help/comments.

 

[cyabro]

Pretty sure it won't work because Sbs2003, or any sbs version, has to be the domain controller so can't join another domain.

 

[YeOldeStonecat]

SBS isn't a ''jumped up XP"....its Server 2003, which was the server version out when Windows XP was out, so you could say it's same vintage as Windows XP and some core components are similar in technology.

When you retired the old server, did you begin reinstalling Server 2003? And then before installing SBS components, once Server 03 was installed and sitting at workgroup mode (meaning SBS components and DCPROMO hadn't been run yet), you joined the 2012 active directory?

...of course, this would be against SBS licensing.....if you want to use that old server as a backup storage device (basically a NAS)...just pave it and load FreeNAS on it.

 

[TAPtech]

Two weeks ago I replaced an SBS 2003 box with a 2012 Essentials Box. I just recreated the AD and made a new domain as the migration did not work, even after being "cleared" through the prep tool. It just hung at about 85%.

Can you just create a separate domain? Add a DNS entry to the old server in the 2012 box and let her hum along. Make sure you do not have DHCP running on both servers.

Also, I am pretty sure you can add the XP machines to the domain. The connector tool probably won't work, but if you right click My Computer, properties, and change the domain through that route it should hook up fine. It probably won't support the new auto backup tools and such but I don't think you will have a problem with traditional file shares and access policies.

Man, going from that old 2003 box with 100T to a new (and lower end, mind you!) 2012 box with good gigabit hardware is such a huge difference in performance!

 

[Mick]

Thanks all.

SBS isn't a ''jumped up XP"....its Server 2003, which was the server version out when Windows XP was out, so you could say it's same vintage as Windows XP and some core components are similar in technology.

. Point taken - what I mean is, W2012 won't 'see' it for the same reasons as it won't see XP machines - interestingly, the only way I can see ANY clients is by using 2012's dashboard - If you try going Control Panel > Network, you can only see printers and the local drives. Same if you use Explorer or any other way. What I've done to this old box is demote it from DNC status - haven't re-installed anything. I was hoping W21012 would at least recognise it as attached to the network, so I could choose it as the back-up location, but no luck, although I've tried several back-up programs as well as the Windows native.
Taptech: Yes - you can join XP machines to the domain - and I've joined this old box manually - but W2012 still refuses to recognise it. I think the suggestion of FreeNAS is probably the way to go - just hope W2012 is in a good mood and will deign to recognise it then!

 

[YeOldeStonecat]

What I've done to this old box is demote it from DNC status - haven't re-installed anything. !

What you'll find after a month or so, is there is a hidden service called sbcore or something like that, which will start rebooting the server on an hourly basis. Microsoft programmed SBS to be the head honcho DC...if it's anything else....hourly reboots to remind you that you're using it outside of its licensing.

 

[Mick]

Thanks. Well, that kind of settles it then... N 'n' P here I come..!

 

[TAPtech]

Mick, when you say that 2012 won't "see" the XP machines, do you just mean through the Dashboard?

You should be able to Map a drive to the old server.

 

[Mick]

Yes, I'd have thought so too - but I can't! It's not showing up on the new server. Interestingly, if I look at mapping the new server from the old, that doesn't show up either. So, despite telling me otherwise, it doesn't look to me as if this machine is successfully joined to the domain.

 

[TAPtech]

Can you just map it using the IP addy and not trying to use the computer name?

I have a client right now with a SBS 2003 box and a 2012 essentials box sitting right next to each other. Same subnet. TWO domains, each is a DC. The ASUS router does DHCP (I don't know 2012 Essentials even does DHCP.)

BOTH boxes are set up for DNS right now as the only thing the 2003 box is doing is serving 1 old XP machine that will be replaced in a week or two.

I think that I can find the old 2003 box by name, but I can absolutely map to it using its IP addy.

Stonecat mentioned some SBS issues with DC requirements. I really have no clue in that area, but taking his advice (which is always a good idea) maybe it would be best to just let the old 2003 box control a domain where the DC is the only computer on it. It might be lonely but who cares.

 

[Mick]

Some good thoughts - thanks. I'll have another look at it on Monday when I'm next over at my clients. Will post back if I have any luck! Oh - btw - W Essentials does do DHCP, and this one is set up to do so.

 

[Mick]

Ah well - no luck any which way. These machines resolutely refuse to see each other. I'm sure there must be a way round this, but I'm going to cut my losses and convert the old box to a freeNAS. Life's too short...
Thanks for your help, guys.

 

[YeOldeStonecat]

Ah well - no luck any which way. These machines resolutely refuse to see each other. I'm sure there must be a way round this, but I'm going to cut my losses and convert the old box to a freeNAS. Life's too short...
Thanks for your help, guys.

It's the correct thing to do with licensing anyways, as leaving it a member server is against Microsofts TOS....it's a pizza tech hack technique.