Q's on upgrade from Win Server 2003 to Win SBS 2003

Hi Folks,

I have a customer that wants to upgrade from Win Server 2003
Standard Edition to Win Small Business Server 2003. They also want to
move to a new server at the same time. Microsoft has told me that this
is an OK upgrade path. Since I don't have a lot of experience with the
Win Server products I was looking for some feedback on how to proceed.
I can think of two ways to do this but maybe there is a better way
still ?

1. Upgrade in place on the old server then do a backup and then a
restore on the new server. I am a bit concerned because it seems to me
that NT-derived OS's seem to not do well when mucho hardware is
changed, they seem to fail in booting commonly in these circumstances.
Perhaps a re-install (upgrade/repair) at this point would help ?

2. Install SBS on the new PC. Export all the user info such as
name/password info (can this be done ?) and import it in the new PC.
Xfr over the user data. Some how track down all the non user info
(networking stuff, ...) and setup that info on the new PC.

There's got to be a good way !

Thanks,
Denis

Denisf@comcast.net

Henry
Thu Oct 14 03:29:38 CDT 2004

So what's the current setup ?
What's the Server running ?
AD Domain ? Other servers ( Exchange, IIS, SQL etc... ) ? Workgroup /
file and print only ? How many workstations ?

etc....

--
Henry Craven {SBS-MVP}
Melbourne Australia


<denisf@comcast.net> wrote in message
news:3tprm0h1fcmfchj899afrlpskg6946ktsp@4ax.com...
> Hi Folks,
>
> I have a customer that wants to upgrade from Win Server 2003
> Standard Edition to Win Small Business Server 2003. They also want to
> move to a new server at the same time. Microsoft has told me that this
> is an OK upgrade path. Since I don't have a lot of experience with the
> Win Server products I was looking for some feedback on how to proceed.
> I can think of two ways to do this but maybe there is a better way
> still ?
>
> 1. Upgrade in place on the old server then do a backup and then a
> restore on the new server. I am a bit concerned because it seems to me
> that NT-derived OS's seem to not do well when mucho hardware is
> changed, they seem to fail in booting commonly in these circumstances.
> Perhaps a re-install (upgrade/repair) at this point would help ?
>
> 2. Install SBS on the new PC. Export all the user info such as
> name/password info (can this be done ?) and import it in the new PC.
> Xfr over the user data. Some how track down all the non user info
> (networking stuff, ...) and setup that info on the new PC.
>
> There's got to be a good way !
>
> Thanks,
> Denis
>
> Denisf@comcast.net
>
>
>
>

denisf
Thu Oct 14 06:26:13 CDT 2004

Current setup is Win Server 2003 Std Edition. Not running Exchange,
IIS SQL or anything else ! Just a file server really. It is in a
workgroup, not a domain. About 20 workstations. This upgrade is
primarily to start using Exchange, but I saw that is phase two after
the PC move and the s/w upgrade.

On Thu, 14 Oct 2004 18:29:38 +1000, "Henry Craven" <IUnknown@Dot.Nyet>
wrote:

>So what's the current setup ?
>What's the Server running ?
>AD Domain ? Other servers ( Exchange, IIS, SQL etc... ) ? Workgroup /
>file and print only ? How many workstations ?
>
>etc....
>
>--
>Henry Craven {SBS-MVP}
> Melbourne Australia
>
>
><denisf@comcast.net> wrote in message
>news:3tprm0h1fcmfchj899afrlpskg6946ktsp@4ax.com...
>> Hi Folks,
>>
>> I have a customer that wants to upgrade from Win Server 2003
>> Standard Edition to Win Small Business Server 2003. They also want to
>> move to a new server at the same time. Microsoft has told me that this
>> is an OK upgrade path. Since I don't have a lot of experience with the
>> Win Server products I was looking for some feedback on how to proceed.
>> I can think of two ways to do this but maybe there is a better way
>> still ?
>>
>> 1. Upgrade in place on the old server then do a backup and then a
>> restore on the new server. I am a bit concerned because it seems to me
>> that NT-derived OS's seem to not do well when mucho hardware is
>> changed, they seem to fail in booting commonly in these circumstances.
>> Perhaps a re-install (upgrade/repair) at this point would help ?
>>
>> 2. Install SBS on the new PC. Export all the user info such as
>> name/password info (can this be done ?) and import it in the new PC.
>> Xfr over the user data. Some how track down all the non user info
>> (networking stuff, ...) and setup that info on the new PC.
>>
>> There's got to be a good way !
>>
>> Thanks,
>> Denis
>>
>> Denisf@comcast.net
>>
>>
>>
>>
>

Henry
Thu Oct 14 11:04:08 CDT 2004

Pretty simple upgrade then really.
Backup your data from the existing server, Build and install the new
SBServer, Join the workstations to the new Domain, Restore the Data
files onto the SBServer, Enable folder re-direction and have the users
copy any local data to their DataStores on the server, and their local
mail stores to their exchange/outlook mailboxes.

--
Henry Craven {SBS-MVP}
Melbourne Australia

<denisf@attbi.com> wrote in message
news:39osm05gjpail43en55qrc3va6qu730e8n@4ax.com...
> Current setup is Win Server 2003 Std Edition. Not running Exchange,
> IIS SQL or anything else ! Just a file server really. It is in a
> workgroup, not a domain. About 20 workstations. This upgrade is
> primarily to start using Exchange, but I saw that is phase two after
> the PC move and the s/w upgrade.
>
> On Thu, 14 Oct 2004 18:29:38 +1000, "Henry Craven" <IUnknown@Dot.Nyet>
> wrote:
>
> >So what's the current setup ?
> >What's the Server running ?
> >AD Domain ? Other servers ( Exchange, IIS, SQL etc... ) ? Workgroup /
> >file and print only ? How many workstations ?
> >
> >etc....
> >
> >--
> >Henry Craven {SBS-MVP}
> > Melbourne Australia

denisf
Thu Oct 14 18:24:51 CDT 2004

Hey Henry, thanks for the info.
How would I get the user account info (name/password/...) from the old
to the new server ?

Thanks,
Denis

On Fri, 15 Oct 2004 02:04:08 +1000, "Henry Craven" <IUnknown@Dot.Nyet>
wrote:

>Pretty simple upgrade then really.
>Backup your data from the existing server, Build and install the new
>SBServer, Join the workstations to the new Domain, Restore the Data
>files onto the SBServer, Enable folder re-direction and have the users
>copy any local data to their DataStores on the server, and their local
>mail stores to their exchange/outlook mailboxes.
>
>--
>Henry Craven {SBS-MVP}
> Melbourne Australia
>
><denisf@attbi.com> wrote in message
>news:39osm05gjpail43en55qrc3va6qu730e8n@4ax.com...
>> Current setup is Win Server 2003 Std Edition. Not running Exchange,
>> IIS SQL or anything else ! Just a file server really. It is in a
>> workgroup, not a domain. About 20 workstations. This upgrade is
>> primarily to start using Exchange, but I saw that is phase two after
>> the PC move and the s/w upgrade.
>>
>> On Thu, 14 Oct 2004 18:29:38 +1000, "Henry Craven" <IUnknown@Dot.Nyet>
>> wrote:
>>
>> >So what's the current setup ?
>> >What's the Server running ?
>> >AD Domain ? Other servers ( Exchange, IIS, SQL etc... ) ? Workgroup /
>> >file and print only ? How many workstations ?
>> >
>> >etc....
>> >
>> >--
>> >Henry Craven {SBS-MVP}
>> > Melbourne Australia
>

Henry
Thu Oct 14 18:59:30 CDT 2004

Wouldn't bother.
There is no central repository in a Workgroup for the Users details as
there is in a Domain. ( ...just one of the Advantages of an AD Domain )

As you're going from a Workgroup to a Domain, the Domain Profile will be
different from the Workgroup profile anyway so users will get new
Desktops, (but if they are XP Clients you can migrate the profiles, or
otherwise manually copy them across).

So, you'll need to get all the user.names ( particularly their e'mail
names manually.
As far as passwords go, this is a good time to enforce Complex
PassPhrases and Password timeout and re-use limits to enhance your
security.

While it's a "Simple" upgrade, I didn't say there wouldn't be a good
deal of work involved. ;-)

--
Henry Craven {SBS-MVP}
Melbourne Australia


<denisf@attbi.com> wrote in message
news:561um0lba4kkjqo44mdge7vg8kh2pv92co@4ax.com...
> Hey Henry, thanks for the info.
> How would I get the user account info (name/password/...) from the old
> to the new server ?
>
> Thanks,
> Denis
>
> On Fri, 15 Oct 2004 02:04:08 +1000, "Henry Craven" <IUnknown@Dot.Nyet>
> wrote:
>
> >Pretty simple upgrade then really.
> >Backup your data from the existing server, Build and install the new
> >SBServer, Join the workstations to the new Domain, Restore the Data
> >files onto the SBServer, Enable folder re-direction and have the
users
> >copy any local data to their DataStores on the server, and their
local
> >mail stores to their exchange/outlook mailboxes.
> >
> >--
> >Henry Craven {SBS-MVP}
> > Melbourne Australia
> >
> ><denisf@attbi.com> wrote in message
> >news:39osm05gjpail43en55qrc3va6qu730e8n@4ax.com...
> >> Current setup is Win Server 2003 Std Edition. Not running Exchange,
> >> IIS SQL or anything else ! Just a file server really. It is in a
> >> workgroup, not a domain. About 20 workstations. This upgrade is
> >> primarily to start using Exchange, but I saw that is phase two
after
> >> the PC move and the s/w upgrade.
> >>
> >> On Thu, 14 Oct 2004 18:29:38 +1000, "Henry Craven"
<IUnknown@Dot.Nyet>
> >> wrote:
> >>
> >> >So what's the current setup ?
> >> >What's the Server running ?
> >> >AD Domain ? Other servers ( Exchange, IIS, SQL etc... ) ?
Workgroup /
> >> >file and print only ? How many workstations ?
> >> >
> >> >etc....
> >> >
> >> >--
> >> >Henry Craven {SBS-MVP}
> >> > Melbourne Australia
> >
>

denisf
Thu Oct 14 20:10:42 CDT 2004

Sorry for my ignorance but I assumed that they would stay workgroup
based rather than domain based. The primary reason to upgrade to SBS
was to start using Exchange for email and scheduling. Does that fact
imply anything else I need to know or do ? Do I have to go to domain
based serving ? If so, any pointers to info about that that you may be
able to offer.

Many thanks for all the help you have provided,
Denis


On Fri, 15 Oct 2004 09:59:30 +1000, "Henry Craven" <IUnknown@Dot.Nyet>
wrote:

>Wouldn't bother.
>There is no central repository in a Workgroup for the Users details as
>there is in a Domain. ( ...just one of the Advantages of an AD Domain )
>
>As you're going from a Workgroup to a Domain, the Domain Profile will be
>different from the Workgroup profile anyway so users will get new
>Desktops, (but if they are XP Clients you can migrate the profiles, or
>otherwise manually copy them across).
>
>So, you'll need to get all the user.names ( particularly their e'mail
>names manually.
>As far as passwords go, this is a good time to enforce Complex
>PassPhrases and Password timeout and re-use limits to enhance your
>security.
>
>While it's a "Simple" upgrade, I didn't say there wouldn't be a good
>deal of work involved. ;-)
>
>--
>Henry Craven {SBS-MVP}
> Melbourne Australia
>
>
><denisf@attbi.com> wrote in message
>news:561um0lba4kkjqo44mdge7vg8kh2pv92co@4ax.com...
>> Hey Henry, thanks for the info.
>> How would I get the user account info (name/password/...) from the old
>> to the new server ?
>>
>> Thanks,
>> Denis
>>
>> On Fri, 15 Oct 2004 02:04:08 +1000, "Henry Craven" <IUnknown@Dot.Nyet>
>> wrote:
>>
>> >Pretty simple upgrade then really.
>> >Backup your data from the existing server, Build and install the new
>> >SBServer, Join the workstations to the new Domain, Restore the Data
>> >files onto the SBServer, Enable folder re-direction and have the
>users
>> >copy any local data to their DataStores on the server, and their
>local
>> >mail stores to their exchange/outlook mailboxes.
>> >
>> >--
>> >Henry Craven {SBS-MVP}
>> > Melbourne Australia
>> >
>> ><denisf@attbi.com> wrote in message
>> >news:39osm05gjpail43en55qrc3va6qu730e8n@4ax.com...
>> >> Current setup is Win Server 2003 Std Edition. Not running Exchange,
>> >> IIS SQL or anything else ! Just a file server really. It is in a
>> >> workgroup, not a domain. About 20 workstations. This upgrade is
>> >> primarily to start using Exchange, but I saw that is phase two
>after
>> >> the PC move and the s/w upgrade.
>> >>
>> >> On Thu, 14 Oct 2004 18:29:38 +1000, "Henry Craven"
><IUnknown@Dot.Nyet>
>> >> wrote:
>> >>
>> >> >So what's the current setup ?
>> >> >What's the Server running ?
>> >> >AD Domain ? Other servers ( Exchange, IIS, SQL etc... ) ?
>Workgroup /
>> >> >file and print only ? How many workstations ?
>> >> >
>> >> >etc....
>> >> >
>> >> >--
>> >> >Henry Craven {SBS-MVP}
>> >> > Melbourne Australia
>> >
>>
>

Henry
Fri Oct 15 05:03:43 CDT 2004

Denis.
SBS -must- be the root of the forest in a single Active Directory
Domain.
Sorry but it makes absolutely no sense to set-up the Domain and have all
your users as members of a workgroup. If you don't understand that then
I fear you level of IT knowledge makes it really hard of not impossible
to advise you via an intermittent and obviously limited medium such as
Usenet. I'd suggest you hire an experienced SBS Consultant to guide you.

--
Henry Craven {SBS-MVP}
Melbourne Australia


<denisf@attbi.com> wrote in message
news:vm8um0tklkbg4ikmff6dbcf35fa5g254gu@4ax.com...
> Sorry for my ignorance but I assumed that they would stay workgroup
> based rather than domain based. The primary reason to upgrade to SBS
> was to start using Exchange for email and scheduling. Does that fact
> imply anything else I need to know or do ? Do I have to go to domain
> based serving ? If so, any pointers to info about that that you may be
> able to offer.
>
> Many thanks for all the help you have provided,
> Denis

Hollis
Fri Oct 15 16:22:05 CDT 2004

In article <vm8um0tklkbg4ikmff6dbcf35fa5g254gu@4ax.com>, wrote:
> Sorry for my ignorance but I assumed that they would stay workgroup
> based rather than domain based. The primary reason to upgrade to SBS
> was to start using Exchange for email and scheduling. Does that fact
> imply anything else I need to know or do ? Do I have to go to domain
> based serving ? If so, any pointers to info about that that you may be
> able to offer.
>
Denis,

I ran my client computers from the workgroups through all my transitions
from SBS4.0 to 4.5 to 2000 and into 2003. For the same reason, to keep
the same user profile. Of course, it all started because I had two SBS
system boxes and I could just unplug the network cable from one hub and
put it in the other hub and the client worked the same. With SBS2000, I
ran a separate Exchange on a member Win2003 server, and so didn't need a
separate SBS box. Now I am just using the one SBS2003 box, and have had
no Exchange deaths, even through several electrical storm caused power
outages.

I converted two of the clients to domain profiles just to reduce the
logon and credential prompts with a SharePoint box. But the third
client computer, possessively guarded by my wife, who wants no changes
made to her environment, is still as a workgroup. There are only a few
things for which one needs to be logged in on a domain profile, and if
your users are not particularly demanding, or don't know the difference,
you won't really have much problems continuing as you are.

Hollis D. Paul [MVP - Outlook]
Hollis@outhousebythesound.com
Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2600
http://search.support.microsoft.com/kb/c.asp?FR=0&SD=TECH&LN=EN-US

Mukilteo, WA USA

Marina
Fri Oct 15 15:39:49 CDT 2004

Hi Hollis,

You can transfer the profile without any problem when adding the clients to
the domain and I really suggest you do add them to the domain.

--
Regards,

Marina
Microsoft SBS-MVP

"Hollis D. Paul" <Hollis@outhousebythesound.com> schreef in bericht
news:VA.00001bcf.0131426e@obts-outlookdev.outlookbythesound.mukwoods...
> In article <vm8um0tklkbg4ikmff6dbcf35fa5g254gu@4ax.com>, wrote:
> > Sorry for my ignorance but I assumed that they would stay workgroup
> > based rather than domain based. The primary reason to upgrade to SBS
> > was to start using Exchange for email and scheduling. Does that fact
> > imply anything else I need to know or do ? Do I have to go to domain
> > based serving ? If so, any pointers to info about that that you may be
> > able to offer.
> >
> Denis,
>
> I ran my client computers from the workgroups through all my transitions
> from SBS4.0 to 4.5 to 2000 and into 2003. For the same reason, to keep
> the same user profile. Of course, it all started because I had two SBS
> system boxes and I could just unplug the network cable from one hub and
> put it in the other hub and the client worked the same. With SBS2000, I
> ran a separate Exchange on a member Win2003 server, and so didn't need a
> separate SBS box. Now I am just using the one SBS2003 box, and have had
> no Exchange deaths, even through several electrical storm caused power
> outages.
>
> I converted two of the clients to domain profiles just to reduce the
> logon and credential prompts with a SharePoint box. But the third
> client computer, possessively guarded by my wife, who wants no changes
> made to her environment, is still as a workgroup. There are only a few
> things for which one needs to be logged in on a domain profile, and if
> your users are not particularly demanding, or don't know the difference,
> you won't really have much problems continuing as you are.
>
> Hollis D. Paul [MVP - Outlook]
> Hollis@outhousebythesound.com
> Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2600
> http://search.support.microsoft.com/kb/c.asp?FR=0&SD=TECH&LN=EN-US
>
> Mukilteo, WA USA
>
>

Hollis
Sat Oct 16 00:56:12 CDT 2004

In article <uRkdfcvsEHA.1308@tk2msftngp13.phx.gbl>, Marina Roos [SBS-MVP]
wrote:
> You can transfer the profile without any problem when adding the clients to
> the domain and I really suggest you do add them to the domain.
>
The profile transfer wizard is really geared to transferring between old and
new hardware. I did not find an adequate utility that would transfer
directories within a single partition. The manual transfer is certainly a
hassle. I have converted both of the client computers that I use to domain
logins, but won't even attempt to touch my wife's computer till she asks me
to do so. So far, she hasn't needed any of the added functionality.

Hollis D. Paul [MVP - Outlook]
Hollis@outhousebythesound.com
Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2600
http://search.support.microsoft.com/kb/c.asp?FR=0&SD=TECH&LN=EN-US

Mukilteo, WA USA