165 replies to this topic

[ikon]

Say what? 2025?

Q: How long will customers be able to purchase Windows Home Server 2011?
A: Windows Home Server 2011 will remain available as an OEM embedded product until December 31, 2025, and will remain available in all other current channels until December 31, 2013.

[Joe_Miner]

I'd advise not hacking that one. What has been lost in this also is the death of SBS Standard. Only the Premium model survives.

http://www.mpecsinc....4D6C81117895FBB

In case you have never been to this site, MPECS, Inc, Philip Elder does one of the best jobs I have ever seen with documentation and in particular setup documentation not only from the hardware side but software side too.

OK, Why not downgrade from a domain to a workgroup?

Isn't it just a matter of un-installing the ADCS then use dcpromo to remove the ADDS then just add it to a workgroup?

[ikon]

Have to say, I'm somewhat surprised by the 'anti-domain' posts. While I'm not doing it at the moment, I did run a domain at home for a few years. I never found it a problem. In fact, it made file sharing easier than workgroups - no more having to match up User IDs and passwords on server(s) and clients.... one login to serve them all I really only stopped having a domain because I replaced my WS2K3 with WHS, and it doesn't support domains.

[no-control]

Since no one has seen the interface yet, I hear a lot of discussion about nothing that matters. If we assume this is essentially the 2012 version of WSS2011e (SBS + WHS). If this version carries over the same user management schema. Then managing domain users in SBS2011e was cake! Managing user accounts, sharing and permissions were no different than WHS2011.i shouldn't be any more difficult. I think there is confusion between active directory and a domain controller. You don't have to use AD (if its even in there) you can manage the accounts locally and still have a domain. Again without even seeing the interface controls or the schema, there's no reason for "sky is falling" craziness.

Drive extender gone, touch first interface, whs gone.....grab you pitch forks and torches!!!!

OK, Why not downgrade from a domain to a workgroup?

Why bother? just because a server is in a domain doesn't mean it can't share outside of it. Better yet why not just join the clients to the domain?

Have to say, I'm somewhat surprised by the 'anti-domain' posts. While I'm not doing it at the moment, I did run a domain at home for a few years. I never found it a problem. In fact, it made file sharing easier than workgroups - no more having to match up User IDs and passwords on server(s) and clients.... one login to serve them all I really only stopped having a domain because I replaced my WS2K3 with WHS, and it doesn't support domains.

Agreed. I'm waiting for a compelling argument to not use one, other than "its hard".

[ikon]

Agreed. I'm waiting for a compelling argument to not use one, other than "its hard".

Which it isn't really.

[Joe_Miner]

-snip-
Agreed. I'm waiting for a compelling argument to not use one, other than "its hard".

Understood, Many of us are all making big assumptions about the characteristics of S2012e without having seen a beta yet. I just don't have confidence that I could make a trasistion to a mixed environment without impacting WAF. No doubt there's confusion on my part and I'm making it a bigger problem than it is actually.

What it boils down to is having the skill set (that I'm not confident I have) to be able to set it up so that it's "transparent" to the rest of the family. It's very hard to build up my "atta-boys" I would like to avoid burning them up with a "What-the-French-Toast" -- So, I'm ready to learn the way to do this that doesn't/wouldn't/couldn't impact the family. I have a SBSe in a VM -- been playing with it but my progress is slow -- what should I be studying? How should/could I prepare my current environment.

[ikon]

I guess the one thing that could have the biggest impact is the requirement for a password. If you're family has gotten used to the idea of never having to use a password it could be a little tricky. I was just looking at what you can do about passwords. It is possible to change the policy to make a password unnecessary (technically, to allow a blank password), but it's a bit of work, and a lot of people have trouble with it. You have to make changes in several places. Miss one, and it doesn't work. Perhaps you could get the family used to the idea of at least a simple password. That still requires changes to the Domain Security Policy, but not as many

ps. forgive me if I left something out: it's been quite a while since I messed with this stuff.

[jmwills]

I have installed SBS many times and the degree to which that product is automated for install is insanely easy. To me that means the install is scripted but to be honest I have never tried or even read of any one trying to demote from a domain to a workgroup.

it is certainly worth trying and writing an article on. Then again, you may be breaking the EULA.....damn I hate reading those things.

[ikon]

I have downgraded servers in the past from domain members to standalone. I've never done it with SBS, but with other Windows Server versions. I would imagine the process is much the same. There are also 3rd party tools to assist with it.

[jmwills]

SBS is built upon a scripted install....I see pitfalls in this path. Although it is worth trying.

[Joe_Miner]

You guys are filling me with so much confidence

Since we haven't seen the Beta yet it may be a moot point but this gives me something to play around with fro awhile and it looks like there's a couple of chapters I should read on ADDS in 2008R2 Unleashed

While I think the WAF would be close to zero if she had to log into our desktop to use it I think it would go into the negative range quite quickly if she had to log into the HTPC's to watch one of her favorite shows. Right now all the machines she could possibly use do not require a PW or log-in.

[tojoski]

Since no one has seen the interface yet, I hear a lot of discussion about nothing that matters. If we assume this is essentially the 2012 version of WSS2011e (SBS + WHS). If this version carries over the same user management schema. Then managing domain users in SBS2011e was cake! Managing user accounts, sharing and permissions were no different than WHS2011.i shouldn't be any more difficult. I think there is confusion between active directory and a domain controller. You don't have to use AD (if its even in there) you can manage the accounts locally and still have a domain. Again without even seeing the interface controls or the schema, there's no reason for "sky is falling" craziness.

Drive extender gone, touch first interface, whs gone.....grab you pitch forks and torches!!!!



Why bother? just because a server is in a domain doesn't mean it can't share outside of it. Better yet why not just join the clients to the domain?



Agreed. I'm waiting for a compelling argument to not use one, other than "its hard".

Biggest issue I have with running a domain is the requirement that each machine be running Win7 Pro or better. I know a lot of you guys are using technet so the point is mute, but I am that exception that has purchased most of the OS's OEM for the machines that I'm running. There's a $40 diff between Win7 Home Premium and Pro; my wife's laptop, for example came with Home Premium and there is absolutely no reason she needs pro.. so take that into account along with the $425 price tag.

I'm not saying that I will wont eventually migrate to it, but for the time being I'm sticking with my 2011 box.

[ikon]

Biggest issue I have with running a domain is the requirement that each machine be running Win7 Pro or better.

You raise a good point.

[Mr_Smartepants]

Since we haven't seen the Beta yet ...

I don't think there was a beta.

The Server 2012 RC can be downloaded from here:
ISO: http://care.dlservic...3&cprod=w8svrtn
VHD: http://care.dlservic...enter_en-us.exe

[jmwills]

Well, I have my SBSE box downgraded to a workgroup and other than removing a couple of roles and altering a DNS entry, it did not pose any issues, so far. I probably broke the EULA but I'm testing so come and lock me up.

I did take a snapshot of the box before attempting this so going back is no issue. The next thing to do is join a client and see what happens..

[Joe_Miner]

Well, I have my SBSE box downgraded to a workgroup and other than removing a couple of roles and altering a DNS entry, it did not pose any issues, so far. I probably broke the EULA but I'm testing so come and lock me up.

I did take a snapshot of the box before attempting this so going back is no issue. The next thing to do is join a client and see what happens..

Yes, I've done the same -- it's fairly easy actually --:

Remove the Role for Active Directory Certificate Services
Reboot
Go into Command Prompt as Administrator and run dcpromo
Go thru the Wizzard -- since this was a fresh install in VM -- I didn't worry about the warnings (OK, maybe I did) and worked my way thru the wizzard
It'll ask for a new PW for the Administrator Account
Reboot
There you are in the wonderful world of workgroups
I can now see SBS2011e and SBS2011e can see all of my other PC's & Servers

I took a couple of snapshots before doing this so I can go back
I'm going to have to create a VM of a test Client to try Joining to SBS2011e now.

[jmwills]

YOu need to look thru the Event logs....tons of errors about DNS entries. Or at least there was on mine.

[jmwills]

I cannot confirm this but I think demoting the SBSE box from a DC breaks the Dashboard or there is some registry setting that needs adjudicating! I can ping the server, but not vice versa. I can map the default shares from the Server to the client.

Certainly not something I am willing to trust my data to at this point. More testing to come.

[Joe_Miner]

I cannot confirm this but I think demoting the SBSE box from a DC breaks the Dashboard or there is some registry setting that needs adjudicating! I can ping the server, but not vice versa. I can map the default shares from the Server to the client.

Certainly not something I am willing to trust my data to at this point. More testing to come.

Needs more thinking over -- I can download the connector but it fails when executing.

[ikon]

These things aren't too surprising really. Keep at it; I'm betting you can get it sorted out. 'Course, if you do succeed, MS will figure out some way to break it on you