Small Business Server extra "junk" group policies, etc.?

[Guest Joe Murphy]

What was the purpose behind Small Business Server 2003?

 

I just started at a new IT group and SBS was installed on the DC well before

I got here. I'm finding all manner of extra "turds" all over the place,

including group policies like "Small Business Server Lockout Policy" and

"Small Business Server Windows Firewall"

 

It looks like these were pre-baked policies that came with the OS for, well,

"small" businesses so they wouldn't have to do much heavy lifting. Makes

sense, in a way, but I'm ready to ditch some of this stuff and create my own

policies. Any reason why I should keep them?

 

Also I see OUs like "MyBusiness" which contain redundant OUs within called

"Computers", "Distribution Groups" etc.

 

Thanks,

JM

[Guest Mark Storm]

Re: Small Business Server extra "junk" group policies, etc.?

 

Joe,

 

I strongly suggest you spending some time over on another newsgroup, to wit:

microsoft.public.windows.server.sbs. There resides a great group of folks

and we spend a lot of time working with the SBS flavor of Windows. Though a

bit of warning, if over there you refer to SBS with terms like "turds" and

"junk" you will most likely be corrected very quickly. :>)

 

SBS sits on, and is built on Windows Server 2003, and comes with a number of

Wizards and other hand-holding props that might be a little off-setting to

IT folks at first. Once you learn it's peculiarities you might be surprised

at just how powerful it is. I have worked with it for three years now and

love it. I find myself many times, when working on a regular Server 2003

box, wishing I had some of the SBS feature set to deal with. Also, realize

that those re the real apps there (like Exchange) not some watered-down

version.

 

Limitations: all SBS services and apps must run on one box (Exchange,

SharePoint, etc...) and it is maxxed at 75 devices and/or users. If you

need to exceed that, or wish to break apart the apps and join the "real"

Server 2003 world, then they offer a Transition Pack to do just that. My

advice right now is to be very careful discarding what you might call SBS

"junk" until you have a better idea of how it all ties together.

 

Microsoft even has a special document on it's SBS Web site that speaks to

"10 Things An IT Admin Need to Know About SBS", would be well worth your

time. Please join us on the SBS newsgroup site mentioned above, we would

luv to have ya...

 

Take care,

 

Mark

 

 

 

"Joe Murphy" <spam@spamthis.com> wrote in message

news:ONfUr8u%23HHA.980@TK2MSFTNGP06.phx.gbl...

> What was the purpose behind Small Business Server 2003?

>

> I just started at a new IT group and SBS was installed on the DC well

> before I got here. I'm finding all manner of extra "turds" all over the

> place, including group policies like "Small Business Server Lockout

> Policy" and "Small Business Server Windows Firewall"

>

> It looks like these were pre-baked policies that came with the OS for,

> well, "small" businesses so they wouldn't have to do much heavy lifting.

> Makes sense, in a way, but I'm ready to ditch some of this stuff and

> create my own policies. Any reason why I should keep them?

>

> Also I see OUs like "MyBusiness" which contain redundant OUs within called

> "Computers", "Distribution Groups" etc.

>

> Thanks,

> JM

>

[Guest Joe Murphy]

Re: Small Business Server extra "junk" group policies, etc.?

 

Point taken about "turds" and "junk" remarks. I was just getting

frustrated with not knowing the SBS environment.

 

Much obliged for your explanation and reading suggestions. Hopefully I

won't get flamed over in the SBS newsgroup.

 

 

On Wed, 19 Sep 2007 16:16:36 -0400, Mark Storm wrote:

> Joe,

>

> I strongly suggest you spending some time over on another newsgroup, to wit:

> microsoft.public.windows.server.sbs. There resides a great group of folks

> and we spend a lot of time working with the SBS flavor of Windows. Though a

> bit of warning, if over there you refer to SBS with terms like "turds" and

> "junk" you will most likely be corrected very quickly. :>)

>

> SBS sits on, and is built on Windows Server 2003, and comes with a number of

> Wizards and other hand-holding props that might be a little off-setting to

> IT folks at first. Once you learn it's peculiarities you might be surprised

> at just how powerful it is. I have worked with it for three years now and

> love it. I find myself many times, when working on a regular Server 2003

> box, wishing I had some of the SBS feature set to deal with. Also, realize

> that those re the real apps there (like Exchange) not some watered-down

> version.

>

> Limitations: all SBS services and apps must run on one box (Exchange,

> SharePoint, etc...) and it is maxxed at 75 devices and/or users. If you

> need to exceed that, or wish to break apart the apps and join the "real"

> Server 2003 world, then they offer a Transition Pack to do just that. My

> advice right now is to be very careful discarding what you might call SBS

> "junk" until you have a better idea of how it all ties together.

>

> Microsoft even has a special document on it's SBS Web site that speaks to

> "10 Things An IT Admin Need to Know About SBS", would be well worth your

> time. Please join us on the SBS newsgroup site mentioned above, we would

> luv to have ya...

>

> Take care,

>

> Mark

>

>

>

> "Joe Murphy" <spam@spamthis.com> wrote in message

> news:ONfUr8u%23HHA.980@TK2MSFTNGP06.phx.gbl...

>> What was the purpose behind Small Business Server 2003?

>>

>> I just started at a new IT group and SBS was installed on the DC well

>> before I got here. I'm finding all manner of extra "turds" all over the

>> place, including group policies like "Small Business Server Lockout

>> Policy" and "Small Business Server Windows Firewall"

>>

>> It looks like these were pre-baked policies that came with the OS for,

>> well, "small" businesses so they wouldn't have to do much heavy lifting.

>> Makes sense, in a way, but I'm ready to ditch some of this stuff and

>> create my own policies. Any reason why I should keep them?

>>

>> Also I see OUs like "MyBusiness" which contain redundant OUs within called

>> "Computers", "Distribution Groups" etc.

>>

>> Thanks,

>> JM

>>