Re: SBS wizards
- From: "Bill Sanderson" <bill_sanderson@xxxxxxxxxxxxxxxxx>
- Date: Fri, 22 Aug 2008 19:37:30 -0400
Here's an example: If you want to have an Exchange address which forwards to a non-exchange external address, you cannot do this through the wizards. Doing it won't break the server, but it does leave you with some non-standard stuff you need to remember that you did.
You may wish to have FTP available in both directions--the wizards will reset this.
So, you'll need to remember this property of the wizard, and reset it each time you use ceicw.
Use the wizards, but don't be too afraid of the occasional minor tweak which can't be done using them. Document those tweaks, though--because you may need to re-do them.
"Andreas Y." <ayiangoullis@xxxxxxxxxxx> wrote in message news:CDDD987D-C733-47FC-A1E0-0D664620B3AB@xxxxxxxxxxxxxxxx
Thanks to all. I know that it's better to use wizards but I wanted to clarify this comment:
"5: Use the wizards:
The best way to break Windows Small Business Server 2003 is to try configuring systems and processes manually."
From this article:
http://articles.techrepublic.com.com/5100-10878_11-6114222.html
"Cliff Galiher" <cgaliher@xxxxxxxxx> wrote in message news:3pudnf96VaiS9DPVnZ2dnUVZ_o7inZ2d@xxxxxxxxxxxxxxNot to split hairs, but I guess it depends on your definition of "break."
SBS2k3 *is* based on win2k3 and uses the same active directory schema. So, if you administer a box without the wizards, you will not corrupt AD, nor will you 'break' the server in the sense that the server itself is damaged, corrupt, or broken.
Now, with that said, the tools that allow you to configure the server are powerful, and thus it is very easy to misconfigure your server and create problems. THAT would qualify as broken to some people. I don't consider that 'broken' in the traditional sense. The wizards only present a limited subset of options so misconfiguration is more easily avoided. But this comes at the limitation where more exotic configuratoins cannot be achieved with the wizard. Of course, in a small business (the SB in SBS) those edge cases are *extremely* rare and thus, if you want to avoid CEICW for some reason, you should probably ask yourself why first.
The same rules apply to the other wizards. They will not 'break' your server, but they do make certain assumptions and fill in certain defaults when creating users/computers or doing other tasks, that if you were to do manually, you'd have to take extra care to make sure you don't miss. Failing to do so can result in odd errors, apparently random behavior, and difficult-to-track issues. Is the server broken? No. But the data in AD is perhaps inaccurate, or perhaps a group policy is not properly set up to achieve the desired result. The wizard avoids 99% of these complications. And I would again suggest asking the question "am I avoiding the wizard for a reason?" Perhaps the problem isn't the wizard, but in understanding why things are done they way they are.
So...I hope that helps illuminate some things and answers your question. I'd *highly* recommend sticking to the wizards, and if you feel you have a reason not to...post here explaining what your desired result is and perhaps we can help you find a solution that fits your needs.
-Cliff
"Andreas Y." <ayiangoullis@xxxxxxxxxxx> wrote in message news:4FE422DE-FEB9-4278-90A2-C225CBABEF3D@xxxxxxxxxxxxxxxxIs it true that with SBS 2003, if you bypass the wizards and administer manually (i.e. create user accounts), you have big chances of breaking the server?
.
- References:
- Re: SBS wizards
- From: Cliff Galiher
- Re: SBS wizards
- From: Andreas Y.
- Re: SBS wizards
- Prev by Date: Re: public web site
- Next by Date: 2008 features?
- Previous by thread: Re: SBS wizards
- Next by thread: Re: SBS wizards
- Index(es):
Relevant Pages
|
