Do I need my W2K3 Server to be a Domain Controller

[Mark]

Hi and Thanks for helping.

We have a W2K3 Server that is accessed by to local PC's and 2 remote PC's
Obviously at this point onlt 2 people at a time can be in.

We are expanding and I am going to assign the server Terminal Server Role
and add 5 CALS.

I see that somewhere along installation a few years ago, I gave this server
a role of Domain Controll which I see is directly connected to Active
Directory.

Do I need The Domain Controller Role. All we will be doing is accessing a
main software application. NO email, or web hosting at this point.

If I turn off Domain Controller to save memory, will the 2 users remote or
local, still have normal access to the server until I switch over to Terminal
Services.

The other roles that I switched on are, Print Server, (but) it's not really
going that. there is a printer hooked to it. DNS server??, DHCP Server?? and
Wins Server?? Do I need all these on?

We have Microsoft Office on the Server and an Avition multi use software
program. This is all it does.

Can you set me straight a bit? It seems that as time goes by and I do not
use this thing I forget all I learned.

We are going to want 5 users 3 local and 2 remote to access simo.

Thanks.

Mark

 

[Vera Noest [MVP]]

Re: Do I need my W2K3 Server to be a Domain Controller

It is recommended that a Terminal Server runs on a member server in
the domain, not on a DC.
But before you remove any of the roles that the server currently
has, make sure that you have another server which has these roles.
You must have a DC, DHCP, DNS and possibly a WINS server in your
domain, but they don't need to (and shouldn't) run on your terminal
server.
If you decide to demote the server to be a member server in the
domain, remote Desktop access will continue to work just as it does
now, i.e. you will still have 2 concurrent connections (+ one to
the console of the server).

Note that before installing Terminal Services on the server, you
will need to uninstall all user applications from it, then install
TS, and then re-install the user applications again.

Installing applications on a Terminal server must be done while the
server is in "install mode", to ensure multi-user functionality.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com> wrote on 07
okt 2007 in microsoft.public.windows.terminal_services:

> Hi and Thanks for helping.
>
> We have a W2K3 Server that is accessed by to local PC's and 2
> remote PC's Obviously at this point onlt 2 people at a time can
> be in.
>
> We are expanding and I am going to assign the server Terminal
> Server Role and add 5 CALS.
>
> I see that somewhere along installation a few years ago, I gave
> this server a role of Domain Controll which I see is directly
> connected to Active Directory.
>
> Do I need The Domain Controller Role. All we will be doing is
> accessing a main software application. NO email, or web hosting
> at this point.
>
> If I turn off Domain Controller to save memory, will the 2 users
> remote or local, still have normal access to the server until I
> switch over to Terminal Services.
>
> The other roles that I switched on are, Print Server, (but) it's
> not really going that. there is a printer hooked to it. DNS
> server??, DHCP Server?? and Wins Server?? Do I need all these
> on?
>
> We have Microsoft Office on the Server and an Avition multi use
> software program. This is all it does.
>
> Can you set me straight a bit? It seems that as time goes by and
> I do not use this thing I forget all I learned.
>
> We are going to want 5 users 3 local and 2 remote to access
> simo.
>
> Thanks.
>
> Mark

 

[Mark]

Re: Do I need my W2K3 Server to be a Domain Controller

Thank you Vera,

I understood 99% (yeah right). This is shoulda coulda, woulda

There is 1 Server. It will run 1 major multi user program.( and Probably a
New MS Office) No 2nd server.

So I am guessing here that I leave the roles that are turned on?? ON?

2nd I must uninstall Office, and Quickbooks, and re-install them during the
install mode of Terminal Services. The data files and .docs, .xls do they
remain in the Server? Or should I make a back up and drop them back in after
the install?

This statement: that programs must be installed during the TS install mode
to be multi user!!! Is that to say that AFTER I have the TS running with 5
Cals, I can not place a NEW Muli-User Program in the system.?

Everything I am doing here revolves around this: Right now we only can get
to access' to the Server at one time. TS will allow more based on Cals. We
need 5-10 and I will buy them as we go.

The Big Program is going to be remotely uploaded from the seller company.
Can this be done "during" TS install mode. Or can I have them do it After?

Thank you, Thank you...very much

Mark

"Vera Noest [MVP]" wrote:

> It is recommended that a Terminal Server runs on a member server in
> the domain, not on a DC.
> But before you remove any of the roles that the server currently
> has, make sure that you have another server which has these roles.
> You must have a DC, DHCP, DNS and possibly a WINS server in your
> domain, but they don't need to (and shouldn't) run on your terminal
> server.
> If you decide to demote the server to be a member server in the
> domain, remote Desktop access will continue to work just as it does
> now, i.e. you will still have 2 concurrent connections (+ one to
> the console of the server).
>
> Note that before installing Terminal Services on the server, you
> will need to uninstall all user applications from it, then install
> TS, and then re-install the user applications again.
>
> Installing applications on a Terminal server must be done while the
> server is in "install mode", to ensure multi-user functionality.
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com> wrote on 07
> okt 2007 in microsoft.public.windows.terminal_services:
>
> > Hi and Thanks for helping.
> >
> > We have a W2K3 Server that is accessed by to local PC's and 2
> > remote PC's Obviously at this point onlt 2 people at a time can
> > be in.
> >
> > We are expanding and I am going to assign the server Terminal
> > Server Role and add 5 CALS.
> >
> > I see that somewhere along installation a few years ago, I gave
> > this server a role of Domain Controll which I see is directly
> > connected to Active Directory.
> >
> > Do I need The Domain Controller Role. All we will be doing is
> > accessing a main software application. NO email, or web hosting
> > at this point.
> >
> > If I turn off Domain Controller to save memory, will the 2 users
> > remote or local, still have normal access to the server until I
> > switch over to Terminal Services.
> >
> > The other roles that I switched on are, Print Server, (but) it's
> > not really going that. there is a printer hooked to it. DNS
> > server??, DHCP Server?? and Wins Server?? Do I need all these
> > on?
> >
> > We have Microsoft Office on the Server and an Avition multi use
> > software program. This is all it does.
> >
> > Can you set me straight a bit? It seems that as time goes by and
> > I do not use this thing I forget all I learned.
> >
> > We are going to want 5 users 3 local and 2 remote to access
> > simo.
> >
> > Thanks.
> >
> > Mark
>

 

[Vera Noest [MVP]]

Re: Do I need my W2K3 Server to be a Domain Controller

OK, I was assuming that you had another server. Let me rephrase
your options:

If you uninstall the Domain Controller role, you will not have a
domain anymore, nor Active Directory, just a standalone server in a
workgroup. This is such a major decision, that I cannot advice you
on whether to do this or not. Most likely, you'll want to keep your
domain.
That means that you must keep all of the roles that the server
currently has.

That leaves you with no choice than to install Terminal Services on
your Domain Controller. This is not recommended, for both security
and performance reasons, but in very small environments, it can be
done.

As I mentioned, you must uninstall all user applications before you
install Terminal Services. Then install Terminal Services (and the
TS Services Licensing Server) and reboot the server. You don't
install any applications at this stage.

When the TS role is installed, it is time to install the user
applications again. This must be done when the TS is in "install
mode", but that mode has nothing to do with the installation of the
TS role.

Install mode is a special TS operational mode, in which the server
monitors all changes made by the application's install program to
the registry and the file system. It stores a copy of all these
changes in a special area of the registry, known as the "shadow
area". When the installation of the application is finished, you
put the server back into its normal operational mode, which is
called "execute mode".
You put the server into install mode by typing "change user
/install" (without the quotes) at a command line, and put it back
into execute mode again by typing "change user /execute".
When a user logs on to the Terminal Server with a Remote Desktop
client, the server automatically copies the changes made to the
server during application installation from the shadow area into
the user portion of the registry. This process makes sure that all
users get their own personal settings.
If you later on need to install another user application, you go
through the same process with install mode again. Note that *no*
users should be connected to the TS while it is in install mode!

Recommended reading:

186498 - Terminal Server Application Integration Information
http://support.microsoft.com/?kbid=186498

Applications : QuickBooks
http://ts.veranoest.net/ts_apps_qb.htm

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com> wrote on 07
okt 2007 in microsoft.public.windows.terminal_services:

> Thank you Vera,
>
> I understood 99% (yeah right). This is shoulda coulda, woulda
>
> There is 1 Server. It will run 1 major multi user program.( and
> Probably a New MS Office) No 2nd server.
>
> So I am guessing here that I leave the roles that are turned
> on?? ON?
>
> 2nd I must uninstall Office, and Quickbooks, and re-install them
> during the install mode of Terminal Services. The data files
> and .docs, .xls do they remain in the Server? Or should I make a
> back up and drop them back in after the install?
>
> This statement: that programs must be installed during the TS
> install mode to be multi user!!! Is that to say that AFTER I
> have the TS running with 5 Cals, I can not place a NEW Muli-User
> Program in the system.?
>
> Everything I am doing here revolves around this: Right now we
> only can get to access' to the Server at one time. TS will allow
> more based on Cals. We need 5-10 and I will buy them as we go.
>
> The Big Program is going to be remotely uploaded from the seller
> company. Can this be done "during" TS install mode. Or can I
> have them do it After?
>
> Thank you, Thank you...very much
>
> Mark
>
> "Vera Noest [MVP]" wrote:
>
>> It is recommended that a Terminal Server runs on a member
>> server in the domain, not on a DC.
>> But before you remove any of the roles that the server
>> currently has, make sure that you have another server which has
>> these roles. You must have a DC, DHCP, DNS and possibly a WINS
>> server in your domain, but they don't need to (and shouldn't)
>> run on your terminal server.
>> If you decide to demote the server to be a member server in the
>> domain, remote Desktop access will continue to work just as it
>> does now, i.e. you will still have 2 concurrent connections (+
>> one to the console of the server).
>>
>> Note that before installing Terminal Services on the server,
>> you will need to uninstall all user applications from it, then
>> install TS, and then re-install the user applications again.
>>
>> Installing applications on a Terminal server must be done while
>> the server is in "install mode", to ensure multi-user
>> functionality.
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> =?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com> wrote on
>> 07 okt 2007 in microsoft.public.windows.terminal_services:
>>
>> > Hi and Thanks for helping.
>> >
>> > We have a W2K3 Server that is accessed by to local PC's and 2
>> > remote PC's Obviously at this point onlt 2 people at a time
>> > can be in.
>> >
>> > We are expanding and I am going to assign the server Terminal
>> > Server Role and add 5 CALS.
>> >
>> > I see that somewhere along installation a few years ago, I
>> > gave this server a role of Domain Controll which I see is
>> > directly connected to Active Directory.
>> >
>> > Do I need The Domain Controller Role. All we will be doing is
>> > accessing a main software application. NO email, or web
>> > hosting at this point.
>> >
>> > If I turn off Domain Controller to save memory, will the 2
>> > users remote or local, still have normal access to the server
>> > until I switch over to Terminal Services.
>> >
>> > The other roles that I switched on are, Print Server, (but)
>> > it's not really going that. there is a printer hooked to it.
>> > DNS server??, DHCP Server?? and Wins Server?? Do I need all
>> > these on?
>> >
>> > We have Microsoft Office on the Server and an Avition multi
>> > use software program. This is all it does.
>> >
>> > Can you set me straight a bit? It seems that as time goes by
>> > and I do not use this thing I forget all I learned.
>> >
>> > We are going to want 5 users 3 local and 2 remote to access
>> > simo.
>> >
>> > Thanks.
>> >
>> > Mark

 

[Mark]

Re: Do I need my W2K3 Server to be a Domain Controller

Small group. 2 or 3 people in at a time, no more than 5. OK?

I'm just not sure we ever needed a domain.... What I had hoped for was local
PC's to network with the Server which was running QB2005. Then the problems
began.

1. New PC with Vista Home (problems with QB)(can't hook with domain)
2. #2 PC has XP home. (can't hook with domain.

Seems like Workgroup could be the answer.

No network: So they are remoting in. How dumb! Seems like I kill the domain
and make a workgroup, or upgrade the 2 OS's to Vista Business and have them
network a domain. QB is going away anyway for a system by Quantum.

If I remove the domain:
Will I still remote in via MSTSC and my login? Will that work as normal. I
must have that.

Could the vista machine an xp then network with the server workgroup?

The MSTSC brings up an IP address to connect to (presently 24.153.139.***).
Would that number change on demotion of the domain to workgroup?

I know I am over my head, I just don't want to jump in with both feet. I
just want to put a toe in 1st.

Thank you very very much.

Mark

"Vera Noest [MVP]" wrote:

> OK, I was assuming that you had another server. Let me rephrase
> your options:
>
> If you uninstall the Domain Controller role, you will not have a
> domain anymore, nor Active Directory, just a standalone server in a
> workgroup. This is such a major decision, that I cannot advice you
> on whether to do this or not. Most likely, you'll want to keep your
> domain.
> That means that you must keep all of the roles that the server
> currently has.
>
> That leaves you with no choice than to install Terminal Services on
> your Domain Controller. This is not recommended, for both security
> and performance reasons, but in very small environments, it can be
> done.
>
> As I mentioned, you must uninstall all user applications before you
> install Terminal Services. Then install Terminal Services (and the
> TS Services Licensing Server) and reboot the server. You don't
> install any applications at this stage.
>
> When the TS role is installed, it is time to install the user
> applications again. This must be done when the TS is in "install
> mode", but that mode has nothing to do with the installation of the
> TS role.
>
> Install mode is a special TS operational mode, in which the server
> monitors all changes made by the application's install program to
> the registry and the file system. It stores a copy of all these
> changes in a special area of the registry, known as the "shadow
> area". When the installation of the application is finished, you
> put the server back into its normal operational mode, which is
> called "execute mode".
> You put the server into install mode by typing "change user
> /install" (without the quotes) at a command line, and put it back
> into execute mode again by typing "change user /execute".
> When a user logs on to the Terminal Server with a Remote Desktop
> client, the server automatically copies the changes made to the
> server during application installation from the shadow area into
> the user portion of the registry. This process makes sure that all
> users get their own personal settings.
> If you later on need to install another user application, you go
> through the same process with install mode again. Note that *no*
> users should be connected to the TS while it is in install mode!
>
> Recommended reading:
>
> 186498 - Terminal Server Application Integration Information
> http://support.microsoft.com/?kbid=186498
>
> Applications : QuickBooks
> http://ts.veranoest.net/ts_apps_qb.htm
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com> wrote on 07
> okt 2007 in microsoft.public.windows.terminal_services:
>
> > Thank you Vera,
> >
> > I understood 99% (yeah right). This is shoulda coulda, woulda
> >
> > There is 1 Server. It will run 1 major multi user program.( and
> > Probably a New MS Office) No 2nd server.
> >
> > So I am guessing here that I leave the roles that are turned
> > on?? ON?
> >
> > 2nd I must uninstall Office, and Quickbooks, and re-install them
> > during the install mode of Terminal Services. The data files
> > and .docs, .xls do they remain in the Server? Or should I make a
> > back up and drop them back in after the install?
> >
> > This statement: that programs must be installed during the TS
> > install mode to be multi user!!! Is that to say that AFTER I
> > have the TS running with 5 Cals, I can not place a NEW Muli-User
> > Program in the system.?
> >
> > Everything I am doing here revolves around this: Right now we
> > only can get to access' to the Server at one time. TS will allow
> > more based on Cals. We need 5-10 and I will buy them as we go.
> >
> > The Big Program is going to be remotely uploaded from the seller
> > company. Can this be done "during" TS install mode. Or can I
> > have them do it After?
> >
> > Thank you, Thank you...very much
> >
> > Mark
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> It is recommended that a Terminal Server runs on a member
> >> server in the domain, not on a DC.
> >> But before you remove any of the roles that the server
> >> currently has, make sure that you have another server which has
> >> these roles. You must have a DC, DHCP, DNS and possibly a WINS
> >> server in your domain, but they don't need to (and shouldn't)
> >> run on your terminal server.
> >> If you decide to demote the server to be a member server in the
> >> domain, remote Desktop access will continue to work just as it
> >> does now, i.e. you will still have 2 concurrent connections (+
> >> one to the console of the server).
> >>
> >> Note that before installing Terminal Services on the server,
> >> you will need to uninstall all user applications from it, then
> >> install TS, and then re-install the user applications again.
> >>
> >> Installing applications on a Terminal server must be done while
> >> the server is in "install mode", to ensure multi-user
> >> functionality.
> >>
> >> _________________________________________________________
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> TS troubleshooting: http://ts.veranoest.net
> >> ___ please respond in newsgroup, NOT by private email ___
> >>
> >> =?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com> wrote on
> >> 07 okt 2007 in microsoft.public.windows.terminal_services:
> >>
> >> > Hi and Thanks for helping.
> >> >
> >> > We have a W2K3 Server that is accessed by to local PC's and 2
> >> > remote PC's Obviously at this point onlt 2 people at a time
> >> > can be in.
> >> >
> >> > We are expanding and I am going to assign the server Terminal
> >> > Server Role and add 5 CALS.
> >> >
> >> > I see that somewhere along installation a few years ago, I
> >> > gave this server a role of Domain Controll which I see is
> >> > directly connected to Active Directory.
> >> >
> >> > Do I need The Domain Controller Role. All we will be doing is
> >> > accessing a main software application. NO email, or web
> >> > hosting at this point.
> >> >
> >> > If I turn off Domain Controller to save memory, will the 2
> >> > users remote or local, still have normal access to the server
> >> > until I switch over to Terminal Services.
> >> >
> >> > The other roles that I switched on are, Print Server, (but)
> >> > it's not really going that. there is a printer hooked to it.
> >> > DNS server??, DHCP Server?? and Wins Server?? Do I need all
> >> > these on?
> >> >
> >> > We have Microsoft Office on the Server and an Avition multi
> >> > use software program. This is all it does.
> >> >
> >> > Can you set me straight a bit? It seems that as time goes by
> >> > and I do not use this thing I forget all I learned.
> >> >
> >> > We are going to want 5 users 3 local and 2 remote to access
> >> > simo.
> >> >
> >> > Thanks.
> >> >
> >> > Mark
>

 

[Vera Noest [MVP]]

Re: Do I need my W2K3 Server to be a Domain Controller

Mark, I strongly advice you to hire a consultant, so that you can
describe your business needs in detail and then the consultant can
propose the best environment.
I am not prepared to give advice with such far-reaching
consequences in a newsgroup. The risks that it won't work for you
are just too high, because I will never get the whole picture.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com> wrote on 07
okt 2007 in microsoft.public.windows.terminal_services:

> Small group. 2 or 3 people in at a time, no more than 5. OK?
>
> I'm just not sure we ever needed a domain.... What I had hoped
> for was local PC's to network with the Server which was running
> QB2005. Then the problems began.
>
> 1. New PC with Vista Home (problems with QB)(can't hook with
> domain) 2. #2 PC has XP home. (can't hook with domain.
>
> Seems like Workgroup could be the answer.
>
> No network: So they are remoting in. How dumb! Seems like I kill
> the domain and make a workgroup, or upgrade the 2 OS's to Vista
> Business and have them network a domain. QB is going away
> anyway for a system by Quantum.
>
> If I remove the domain:
> Will I still remote in via MSTSC and my login? Will that work as
> normal. I must have that.
>
> Could the vista machine an xp then network with the server
> workgroup?
>
> The MSTSC brings up an IP address to connect to (presently
> 24.153.139.***). Would that number change on demotion of the
> domain to workgroup?
>
> I know I am over my head, I just don't want to jump in with both
> feet. I just want to put a toe in 1st.
>
> Thank you very very much.
>
> Mark
>
> "Vera Noest [MVP]" wrote:
>
>> OK, I was assuming that you had another server. Let me rephrase
>> your options:
>>
>> If you uninstall the Domain Controller role, you will not have
>> a domain anymore, nor Active Directory, just a standalone
>> server in a workgroup. This is such a major decision, that I
>> cannot advice you on whether to do this or not. Most likely,
>> you'll want to keep your domain.
>> That means that you must keep all of the roles that the server
>> currently has.
>>
>> That leaves you with no choice than to install Terminal
>> Services on your Domain Controller. This is not recommended,
>> for both security and performance reasons, but in very small
>> environments, it can be done.
>>
>> As I mentioned, you must uninstall all user applications before
>> you install Terminal Services. Then install Terminal Services
>> (and the TS Services Licensing Server) and reboot the server.
>> You don't install any applications at this stage.
>>
>> When the TS role is installed, it is time to install the user
>> applications again. This must be done when the TS is in
>> "install mode", but that mode has nothing to do with the
>> installation of the TS role.
>>
>> Install mode is a special TS operational mode, in which the
>> server monitors all changes made by the application's install
>> program to the registry and the file system. It stores a copy
>> of all these changes in a special area of the registry, known
>> as the "shadow area". When the installation of the application
>> is finished, you put the server back into its normal
>> operational mode, which is called "execute mode".
>> You put the server into install mode by typing "change user
>> /install" (without the quotes) at a command line, and put it
>> back into execute mode again by typing "change user /execute".
>> When a user logs on to the Terminal Server with a Remote
>> Desktop client, the server automatically copies the changes
>> made to the server during application installation from the
>> shadow area into the user portion of the registry. This process
>> makes sure that all users get their own personal settings.
>> If you later on need to install another user application, you
>> go through the same process with install mode again. Note that
>> *no* users should be connected to the TS while it is in install
>> mode!
>>
>> Recommended reading:
>>
>> 186498 - Terminal Server Application Integration Information
>> http://support.microsoft.com/?kbid=186498
>>
>> Applications : QuickBooks
>> http://ts.veranoest.net/ts_apps_qb.htm
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> =?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com> wrote on
>> 07 okt 2007 in microsoft.public.windows.terminal_services:
>>
>> > Thank you Vera,
>> >
>> > I understood 99% (yeah right). This is shoulda coulda, woulda
>> >
>> > There is 1 Server. It will run 1 major multi user program.(
>> > and Probably a New MS Office) No 2nd server.
>> >
>> > So I am guessing here that I leave the roles that are turned
>> > on?? ON?
>> >
>> > 2nd I must uninstall Office, and Quickbooks, and re-install
>> > them during the install mode of Terminal Services. The data
>> > files and .docs, .xls do they remain in the Server? Or should
>> > I make a back up and drop them back in after the install?
>> >
>> > This statement: that programs must be installed during the TS
>> > install mode to be multi user!!! Is that to say that AFTER I
>> > have the TS running with 5 Cals, I can not place a NEW
>> > Muli-User Program in the system.?
>> >
>> > Everything I am doing here revolves around this: Right now we
>> > only can get to access' to the Server at one time. TS will
>> > allow more based on Cals. We need 5-10 and I will buy them as
>> > we go.
>> >
>> > The Big Program is going to be remotely uploaded from the
>> > seller company. Can this be done "during" TS install mode. Or
>> > can I have them do it After?
>> >
>> > Thank you, Thank you...very much
>> >
>> > Mark
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> It is recommended that a Terminal Server runs on a member
>> >> server in the domain, not on a DC.
>> >> But before you remove any of the roles that the server
>> >> currently has, make sure that you have another server which
>> >> has these roles. You must have a DC, DHCP, DNS and possibly
>> >> a WINS server in your domain, but they don't need to (and
>> >> shouldn't) run on your terminal server.
>> >> If you decide to demote the server to be a member server in
>> >> the domain, remote Desktop access will continue to work just
>> >> as it does now, i.e. you will still have 2 concurrent
>> >> connections (+ one to the console of the server).
>> >>
>> >> Note that before installing Terminal Services on the server,
>> >> you will need to uninstall all user applications from it,
>> >> then install TS, and then re-install the user applications
>> >> again.
>> >>
>> >> Installing applications on a Terminal server must be done
>> >> while the server is in "install mode", to ensure multi-user
>> >> functionality.
>> >>
>> >> _________________________________________________________
>> >> Vera Noest
>> >> MCSE, CCEA, Microsoft MVP - Terminal Server
>> >> TS troubleshooting: http://ts.veranoest.net
>> >> ___ please respond in newsgroup, NOT by private email ___
>> >>
>> >> =?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com> wrote
>> >> on 07 okt 2007 in
>> >> microsoft.public.windows.terminal_services:
>> >>
>> >> > Hi and Thanks for helping.
>> >> >
>> >> > We have a W2K3 Server that is accessed by to local PC's
>> >> > and 2 remote PC's Obviously at this point onlt 2 people at
>> >> > a time can be in.
>> >> >
>> >> > We are expanding and I am going to assign the server
>> >> > Terminal Server Role and add 5 CALS.
>> >> >
>> >> > I see that somewhere along installation a few years ago, I
>> >> > gave this server a role of Domain Controll which I see is
>> >> > directly connected to Active Directory.
>> >> >
>> >> > Do I need The Domain Controller Role. All we will be doing
>> >> > is accessing a main software application. NO email, or web
>> >> > hosting at this point.
>> >> >
>> >> > If I turn off Domain Controller to save memory, will the 2
>> >> > users remote or local, still have normal access to the
>> >> > server until I switch over to Terminal Services.
>> >> >
>> >> > The other roles that I switched on are, Print Server,
>> >> > (but) it's not really going that. there is a printer
>> >> > hooked to it. DNS server??, DHCP Server?? and Wins
>> >> > Server?? Do I need all these on?
>> >> >
>> >> > We have Microsoft Office on the Server and an Avition
>> >> > multi use software program. This is all it does.
>> >> >
>> >> > Can you set me straight a bit? It seems that as time goes
>> >> > by and I do not use this thing I forget all I learned.
>> >> >
>> >> > We are going to want 5 users 3 local and 2 remote to
>> >> > access simo.
>> >> >
>> >> > Thanks.
>> >> >
>> >> > Mark

 

[Mark]

Re: Do I need my W2K3 Server to be a Domain Controller

I am going to have help on sight!
I was just looking for confirmation of things I believe I have learned.

#1 I keep the domain and make the Server a TS. (get Cals)
#2 Upgrade Vista Home to Business, # 2 PC to Vista Busness or XP PRO. (They
should then network to the domain correct?

#3 Remove all programs, and Turn on TS. reboot. Install programs.
# 4 continue to remote in form 2 sites.

Sound normal? or sorta normal. Believe me. I will not just throw switchs.

Thanks.



"Vera Noest [MVP]" wrote:

> Mark, I strongly advice you to hire a consultant, so that you can
> describe your business needs in detail and then the consultant can
> propose the best environment.
> I am not prepared to give advice with such far-reaching
> consequences in a newsgroup. The risks that it won't work for you
> are just too high, because I will never get the whole picture.
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com> wrote on 07
> okt 2007 in microsoft.public.windows.terminal_services:
>
> > Small group. 2 or 3 people in at a time, no more than 5. OK?
> >
> > I'm just not sure we ever needed a domain.... What I had hoped
> > for was local PC's to network with the Server which was running
> > QB2005. Then the problems began.
> >
> > 1. New PC with Vista Home (problems with QB)(can't hook with
> > domain) 2. #2 PC has XP home. (can't hook with domain.
> >
> > Seems like Workgroup could be the answer.
> >
> > No network: So they are remoting in. How dumb! Seems like I kill
> > the domain and make a workgroup, or upgrade the 2 OS's to Vista
> > Business and have them network a domain. QB is going away
> > anyway for a system by Quantum.
> >
> > If I remove the domain:
> > Will I still remote in via MSTSC and my login? Will that work as
> > normal. I must have that.
> >
> > Could the vista machine an xp then network with the server
> > workgroup?
> >
> > The MSTSC brings up an IP address to connect to (presently
> > 24.153.139.***). Would that number change on demotion of the
> > domain to workgroup?
> >
> > I know I am over my head, I just don't want to jump in with both
> > feet. I just want to put a toe in 1st.
> >
> > Thank you very very much.
> >
> > Mark
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> OK, I was assuming that you had another server. Let me rephrase
> >> your options:
> >>
> >> If you uninstall the Domain Controller role, you will not have
> >> a domain anymore, nor Active Directory, just a standalone
> >> server in a workgroup. This is such a major decision, that I
> >> cannot advice you on whether to do this or not. Most likely,
> >> you'll want to keep your domain.
> >> That means that you must keep all of the roles that the server
> >> currently has.
> >>
> >> That leaves you with no choice than to install Terminal
> >> Services on your Domain Controller. This is not recommended,
> >> for both security and performance reasons, but in very small
> >> environments, it can be done.
> >>
> >> As I mentioned, you must uninstall all user applications before
> >> you install Terminal Services. Then install Terminal Services
> >> (and the TS Services Licensing Server) and reboot the server.
> >> You don't install any applications at this stage.
> >>
> >> When the TS role is installed, it is time to install the user
> >> applications again. This must be done when the TS is in
> >> "install mode", but that mode has nothing to do with the
> >> installation of the TS role.
> >>
> >> Install mode is a special TS operational mode, in which the
> >> server monitors all changes made by the application's install
> >> program to the registry and the file system. It stores a copy
> >> of all these changes in a special area of the registry, known
> >> as the "shadow area". When the installation of the application
> >> is finished, you put the server back into its normal
> >> operational mode, which is called "execute mode".
> >> You put the server into install mode by typing "change user
> >> /install" (without the quotes) at a command line, and put it
> >> back into execute mode again by typing "change user /execute".
> >> When a user logs on to the Terminal Server with a Remote
> >> Desktop client, the server automatically copies the changes
> >> made to the server during application installation from the
> >> shadow area into the user portion of the registry. This process
> >> makes sure that all users get their own personal settings.
> >> If you later on need to install another user application, you
> >> go through the same process with install mode again. Note that
> >> *no* users should be connected to the TS while it is in install
> >> mode!
> >>
> >> Recommended reading:
> >>
> >> 186498 - Terminal Server Application Integration Information
> >> http://support.microsoft.com/?kbid=186498
> >>
> >> Applications : QuickBooks
> >> http://ts.veranoest.net/ts_apps_qb.htm
> >>
> >> _________________________________________________________
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> TS troubleshooting: http://ts.veranoest.net
> >> ___ please respond in newsgroup, NOT by private email ___
> >>
> >> =?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com> wrote on
> >> 07 okt 2007 in microsoft.public.windows.terminal_services:
> >>
> >> > Thank you Vera,
> >> >
> >> > I understood 99% (yeah right). This is shoulda coulda, woulda
> >> >
> >> > There is 1 Server. It will run 1 major multi user program.(
> >> > and Probably a New MS Office) No 2nd server.
> >> >
> >> > So I am guessing here that I leave the roles that are turned
> >> > on?? ON?
> >> >
> >> > 2nd I must uninstall Office, and Quickbooks, and re-install
> >> > them during the install mode of Terminal Services. The data
> >> > files and .docs, .xls do they remain in the Server? Or should
> >> > I make a back up and drop them back in after the install?
> >> >
> >> > This statement: that programs must be installed during the TS
> >> > install mode to be multi user!!! Is that to say that AFTER I
> >> > have the TS running with 5 Cals, I can not place a NEW
> >> > Muli-User Program in the system.?
> >> >
> >> > Everything I am doing here revolves around this: Right now we
> >> > only can get to access' to the Server at one time. TS will
> >> > allow more based on Cals. We need 5-10 and I will buy them as
> >> > we go.
> >> >
> >> > The Big Program is going to be remotely uploaded from the
> >> > seller company. Can this be done "during" TS install mode. Or
> >> > can I have them do it After?
> >> >
> >> > Thank you, Thank you...very much
> >> >
> >> > Mark
> >> >
> >> > "Vera Noest [MVP]" wrote:
> >> >
> >> >> It is recommended that a Terminal Server runs on a member
> >> >> server in the domain, not on a DC.
> >> >> But before you remove any of the roles that the server
> >> >> currently has, make sure that you have another server which
> >> >> has these roles. You must have a DC, DHCP, DNS and possibly
> >> >> a WINS server in your domain, but they don't need to (and
> >> >> shouldn't) run on your terminal server.
> >> >> If you decide to demote the server to be a member server in
> >> >> the domain, remote Desktop access will continue to work just
> >> >> as it does now, i.e. you will still have 2 concurrent
> >> >> connections (+ one to the console of the server).
> >> >>
> >> >> Note that before installing Terminal Services on the server,
> >> >> you will need to uninstall all user applications from it,
> >> >> then install TS, and then re-install the user applications
> >> >> again.
> >> >>
> >> >> Installing applications on a Terminal server must be done
> >> >> while the server is in "install mode", to ensure multi-user
> >> >> functionality.
> >> >>
> >> >> _________________________________________________________
> >> >> Vera Noest
> >> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> >> TS troubleshooting: http://ts.veranoest.net
> >> >> ___ please respond in newsgroup, NOT by private email ___
> >> >>
> >> >> =?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com> wrote
> >> >> on 07 okt 2007 in
> >> >> microsoft.public.windows.terminal_services:
> >> >>
> >> >> > Hi and Thanks for helping.
> >> >> >
> >> >> > We have a W2K3 Server that is accessed by to local PC's
> >> >> > and 2 remote PC's Obviously at this point onlt 2 people at
> >> >> > a time can be in.
> >> >> >
> >> >> > We are expanding and I am going to assign the server
> >> >> > Terminal Server Role and add 5 CALS.
> >> >> >
> >> >> > I see that somewhere along installation a few years ago, I
> >> >> > gave this server a role of Domain Controll which I see is
> >> >> > directly connected to Active Directory.
> >> >> >
> >> >> > Do I need The Domain Controller Role. All we will be doing
> >> >> > is accessing a main software application. NO email, or web
> >> >> > hosting at this point.
> >> >> >
> >> >> > If I turn off Domain Controller to save memory, will the 2
> >> >> > users remote or local, still have normal access to the
> >> >> > server until I switch over to Terminal Services.
> >> >> >
> >> >> > The other roles that I switched on are, Print Server,
> >> >> > (but) it's not really going that. there is a printer
> >> >> > hooked to it. DNS server??, DHCP Server?? and Wins
> >> >> > Server?? Do I need all these on?
> >> >> >
> >> >> > We have Microsoft Office on the Server and an Avition
> >> >> > multi use software program. This is all it does.
> >> >> >
> >> >> > Can you set me straight a bit? It seems that as time goes
> >> >> > by and I do not use this thing I forget all I learned.
> >> >> >
> >> >> > We are going to want 5 users 3 local and 2 remote to
> >> >> > access simo.
> >> >> >
> >> >> > Thanks.
> >> >> >
> >> >> > Mark
>

 

[Vera Noest [MVP]]

Re: Do I need my W2K3 Server to be a Domain Controller

OK, for what it's worth: yes, that sounds OK.
Keep the domain, which means keep all other roles on the server
(DHCP, DNS, etc). The Vista clients will be able to join the
domain.
All clients, whether part of the domain or not, should be able to
rdp into the server (after being upgraded).
Good luck!
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com> wrote on 07
okt 2007 in microsoft.public.windows.terminal_services:

> I am going to have help on sight!
> I was just looking for confirmation of things I believe I have
> learned.
>
> #1 I keep the domain and make the Server a TS. (get Cals)
> #2 Upgrade Vista Home to Business, # 2 PC to Vista Busness or XP
> PRO. (They should then network to the domain correct?
>
> #3 Remove all programs, and Turn on TS. reboot. Install
> programs. # 4 continue to remote in form 2 sites.
>
> Sound normal? or sorta normal. Believe me. I will not just throw
> switchs.
>
> Thanks.
>
>
>
> "Vera Noest [MVP]" wrote:
>
>> Mark, I strongly advice you to hire a consultant, so that you
>> can describe your business needs in detail and then the
>> consultant can propose the best environment.
>> I am not prepared to give advice with such far-reaching
>> consequences in a newsgroup. The risks that it won't work for
>> you are just too high, because I will never get the whole
>> picture.
>> _________________________________________________________ Vera
>> Noest MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> =?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com> wrote on
>> 07 okt 2007 in microsoft.public.windows.terminal_services:
>>
>> > Small group. 2 or 3 people in at a time, no more than 5. OK?
>> >
>> > I'm just not sure we ever needed a domain.... What I had
>> > hoped for was local PC's to network with the Server which was
>> > running QB2005. Then the problems began.
>> >
>> > 1. New PC with Vista Home (problems with QB)(can't hook with
>> > domain) 2. #2 PC has XP home. (can't hook with domain.
>> >
>> > Seems like Workgroup could be the answer.
>> >
>> > No network: So they are remoting in. How dumb! Seems like I
>> > kill the domain and make a workgroup, or upgrade the 2 OS's
>> > to Vista Business and have them network a domain. QB is
>> > going away anyway for a system by Quantum.
>> >
>> > If I remove the domain:
>> > Will I still remote in via MSTSC and my login? Will that work
>> > as normal. I must have that.
>> >
>> > Could the vista machine an xp then network with the server
>> > workgroup?
>> >
>> > The MSTSC brings up an IP address to connect to (presently
>> > 24.153.139.***). Would that number change on demotion of the
>> > domain to workgroup?
>> >
>> > I know I am over my head, I just don't want to jump in with
>> > both feet. I just want to put a toe in 1st.
>> >
>> > Thank you very very much.
>> >
>> > Mark
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> OK, I was assuming that you had another server. Let me
>> >> rephrase your options:
>> >>
>> >> If you uninstall the Domain Controller role, you will not
>> >> have a domain anymore, nor Active Directory, just a
>> >> standalone server in a workgroup. This is such a major
>> >> decision, that I cannot advice you on whether to do this or
>> >> not. Most likely, you'll want to keep your domain.
>> >> That means that you must keep all of the roles that the
>> >> server currently has.
>> >>
>> >> That leaves you with no choice than to install Terminal
>> >> Services on your Domain Controller. This is not recommended,
>> >> for both security and performance reasons, but in very small
>> >> environments, it can be done.
>> >>
>> >> As I mentioned, you must uninstall all user applications
>> >> before you install Terminal Services. Then install Terminal
>> >> Services (and the TS Services Licensing Server) and reboot
>> >> the server. You don't install any applications at this
>> >> stage.
>> >>
>> >> When the TS role is installed, it is time to install the
>> >> user applications again. This must be done when the TS is in
>> >> "install mode", but that mode has nothing to do with the
>> >> installation of the TS role.
>> >>
>> >> Install mode is a special TS operational mode, in which the
>> >> server monitors all changes made by the application's
>> >> install program to the registry and the file system. It
>> >> stores a copy of all these changes in a special area of the
>> >> registry, known as the "shadow area". When the installation
>> >> of the application is finished, you put the server back into
>> >> its normal operational mode, which is called "execute mode".
>> >> You put the server into install mode by typing "change user
>> >> /install" (without the quotes) at a command line, and put it
>> >> back into execute mode again by typing "change user
>> >> /execute". When a user logs on to the Terminal Server with a
>> >> Remote Desktop client, the server automatically copies the
>> >> changes made to the server during application installation
>> >> from the shadow area into the user portion of the registry.
>> >> This process makes sure that all users get their own
>> >> personal settings. If you later on need to install another
>> >> user application, you go through the same process with
>> >> install mode again. Note that *no* users should be connected
>> >> to the TS while it is in install mode!
>> >>
>> >> Recommended reading:
>> >>
>> >> 186498 - Terminal Server Application Integration Information
>> >> http://support.microsoft.com/?kbid=186498
>> >>
>> >> Applications : QuickBooks
>> >> http://ts.veranoest.net/ts_apps_qb.htm
>> >>
>> >> _________________________________________________________
>> >> Vera Noest
>> >> MCSE, CCEA, Microsoft MVP - Terminal Server
>> >> TS troubleshooting: http://ts.veranoest.net
>> >> ___ please respond in newsgroup, NOT by private email ___
>> >>
>> >> =?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com> wrote
>> >> on 07 okt 2007 in
>> >> microsoft.public.windows.terminal_services:
>> >>
>> >> > Thank you Vera,
>> >> >
>> >> > I understood 99% (yeah right). This is shoulda coulda,
>> >> > woulda
>> >> >
>> >> > There is 1 Server. It will run 1 major multi user
>> >> > program.( and Probably a New MS Office) No 2nd server.
>> >> >
>> >> > So I am guessing here that I leave the roles that are
>> >> > turned on?? ON?
>> >> >
>> >> > 2nd I must uninstall Office, and Quickbooks, and
>> >> > re-install them during the install mode of Terminal
>> >> > Services. The data files and .docs, .xls do they remain
>> >> > in the Server? Or should I make a back up and drop them
>> >> > back in after the install?
>> >> >
>> >> > This statement: that programs must be installed during the
>> >> > TS install mode to be multi user!!! Is that to say that
>> >> > AFTER I have the TS running with 5 Cals, I can not place a
>> >> > NEW Muli-User Program in the system.?
>> >> >
>> >> > Everything I am doing here revolves around this: Right now
>> >> > we only can get to access' to the Server at one time. TS
>> >> > will allow more based on Cals. We need 5-10 and I will buy
>> >> > them as we go.
>> >> >
>> >> > The Big Program is going to be remotely uploaded from the
>> >> > seller company. Can this be done "during" TS install mode.
>> >> > Or can I have them do it After?
>> >> >
>> >> > Thank you, Thank you...very much
>> >> >
>> >> > Mark
>> >> >
>> >> > "Vera Noest [MVP]" wrote:
>> >> >
>> >> >> It is recommended that a Terminal Server runs on a member
>> >> >> server in the domain, not on a DC.
>> >> >> But before you remove any of the roles that the server
>> >> >> currently has, make sure that you have another server
>> >> >> which has these roles. You must have a DC, DHCP, DNS and
>> >> >> possibly a WINS server in your domain, but they don't
>> >> >> need to (and shouldn't) run on your terminal server.
>> >> >> If you decide to demote the server to be a member server
>> >> >> in the domain, remote Desktop access will continue to
>> >> >> work just as it does now, i.e. you will still have 2
>> >> >> concurrent connections (+ one to the console of the
>> >> >> server).
>> >> >>
>> >> >> Note that before installing Terminal Services on the
>> >> >> server, you will need to uninstall all user applications
>> >> >> from it, then install TS, and then re-install the user
>> >> >> applications again.
>> >> >>
>> >> >> Installing applications on a Terminal server must be done
>> >> >> while the server is in "install mode", to ensure
>> >> >> multi-user functionality.
>> >> >>
>> >> >> _________________________________________________________
>> >> >> Vera Noest
>> >> >> MCSE, CCEA, Microsoft MVP - Terminal Server
>> >> >> TS troubleshooting: http://ts.veranoest.net
>> >> >> ___ please respond in newsgroup, NOT by private email ___
>> >> >>
>> >> >> =?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com>
>> >> >> wrote on 07 okt 2007 in
>> >> >> microsoft.public.windows.terminal_services:
>> >> >>
>> >> >> > Hi and Thanks for helping.
>> >> >> >
>> >> >> > We have a W2K3 Server that is accessed by to local PC's
>> >> >> > and 2 remote PC's Obviously at this point onlt 2 people
>> >> >> > at a time can be in.
>> >> >> >
>> >> >> > We are expanding and I am going to assign the server
>> >> >> > Terminal Server Role and add 5 CALS.
>> >> >> >
>> >> >> > I see that somewhere along installation a few years
>> >> >> > ago, I gave this server a role of Domain Controll which
>> >> >> > I see is directly connected to Active Directory.
>> >> >> >
>> >> >> > Do I need The Domain Controller Role. All we will be
>> >> >> > doing is accessing a main software application. NO
>> >> >> > email, or web hosting at this point.
>> >> >> >
>> >> >> > If I turn off Domain Controller to save memory, will
>> >> >> > the 2 users remote or local, still have normal access
>> >> >> > to the server until I switch over to Terminal Services.
>> >> >> >
>> >> >> > The other roles that I switched on are, Print Server,
>> >> >> > (but) it's not really going that. there is a printer
>> >> >> > hooked to it. DNS server??, DHCP Server?? and Wins
>> >> >> > Server?? Do I need all these on?
>> >> >> >
>> >> >> > We have Microsoft Office on the Server and an Avition
>> >> >> > multi use software program. This is all it does.
>> >> >> >
>> >> >> > Can you set me straight a bit? It seems that as time
>> >> >> > goes by and I do not use this thing I forget all I
>> >> >> > learned.
>> >> >> >
>> >> >> > We are going to want 5 users 3 local and 2 remote to
>> >> >> > access simo.
>> >> >> >
>> >> >> > Thanks.
>> >> >> >
>> >> >> > Mark

 

[Mark]

Re: Do I need my W2K3 Server to be a Domain Controller

Vera,
I took your advice and sought some IT help. Actually called MS, and they
were a big help.

Plan B: is to Get a dual core (4 Gig) Server to run Quantum and stick a
small 64bit (4 gig) Exchange Server 2007 behind it (don't trust Quantum on 64
bits.)

Server "A" will have TS and W2k3 Standard, and Server 2 will have Exchange
2007 @ 64 bits).

Is there any conflict that you know of, in accessing mail coming from a 64
bit Exchange Server, through to me, Loging into the TS in front at 32 bits?

Whew...in advance.



"Vera Noest [MVP]" wrote:

> OK, for what it's worth: yes, that sounds OK.
> Keep the domain, which means keep all other roles on the server
> (DHCP, DNS, etc). The Vista clients will be able to join the
> domain.
> All clients, whether part of the domain or not, should be able to
> rdp into the server (after being upgraded).
> Good luck!
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com> wrote on 07
> okt 2007 in microsoft.public.windows.terminal_services:
>
> > I am going to have help on sight!
> > I was just looking for confirmation of things I believe I have
> > learned.
> >
> > #1 I keep the domain and make the Server a TS. (get Cals)
> > #2 Upgrade Vista Home to Business, # 2 PC to Vista Busness or XP
> > PRO. (They should then network to the domain correct?
> >
> > #3 Remove all programs, and Turn on TS. reboot. Install
> > programs. # 4 continue to remote in form 2 sites.
> >
> > Sound normal? or sorta normal. Believe me. I will not just throw
> > switchs.
> >
> > Thanks.
> >
> >
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> Mark, I strongly advice you to hire a consultant, so that you
> >> can describe your business needs in detail and then the
> >> consultant can propose the best environment.
> >> I am not prepared to give advice with such far-reaching
> >> consequences in a newsgroup. The risks that it won't work for
> >> you are just too high, because I will never get the whole
> >> picture.
> >> _________________________________________________________ Vera
> >> Noest MCSE, CCEA, Microsoft MVP - Terminal Server
> >> TS troubleshooting: http://ts.veranoest.net
> >> ___ please respond in newsgroup, NOT by private email ___
> >>
> >> =?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com> wrote on
> >> 07 okt 2007 in microsoft.public.windows.terminal_services:
> >>
> >> > Small group. 2 or 3 people in at a time, no more than 5. OK?
> >> >
> >> > I'm just not sure we ever needed a domain.... What I had
> >> > hoped for was local PC's to network with the Server which was
> >> > running QB2005. Then the problems began.
> >> >
> >> > 1. New PC with Vista Home (problems with QB)(can't hook with
> >> > domain) 2. #2 PC has XP home. (can't hook with domain.
> >> >
> >> > Seems like Workgroup could be the answer.
> >> >
> >> > No network: So they are remoting in. How dumb! Seems like I
> >> > kill the domain and make a workgroup, or upgrade the 2 OS's
> >> > to Vista Business and have them network a domain. QB is
> >> > going away anyway for a system by Quantum.
> >> >
> >> > If I remove the domain:
> >> > Will I still remote in via MSTSC and my login? Will that work
> >> > as normal. I must have that.
> >> >
> >> > Could the vista machine an xp then network with the server
> >> > workgroup?
> >> >
> >> > The MSTSC brings up an IP address to connect to (presently
> >> > 24.153.139.***). Would that number change on demotion of the
> >> > domain to workgroup?
> >> >
> >> > I know I am over my head, I just don't want to jump in with
> >> > both feet. I just want to put a toe in 1st.
> >> >
> >> > Thank you very very much.
> >> >
> >> > Mark
> >> >
> >> > "Vera Noest [MVP]" wrote:
> >> >
> >> >> OK, I was assuming that you had another server. Let me
> >> >> rephrase your options:
> >> >>
> >> >> If you uninstall the Domain Controller role, you will not
> >> >> have a domain anymore, nor Active Directory, just a
> >> >> standalone server in a workgroup. This is such a major
> >> >> decision, that I cannot advice you on whether to do this or
> >> >> not. Most likely, you'll want to keep your domain.
> >> >> That means that you must keep all of the roles that the
> >> >> server currently has.
> >> >>
> >> >> That leaves you with no choice than to install Terminal
> >> >> Services on your Domain Controller. This is not recommended,
> >> >> for both security and performance reasons, but in very small
> >> >> environments, it can be done.
> >> >>
> >> >> As I mentioned, you must uninstall all user applications
> >> >> before you install Terminal Services. Then install Terminal
> >> >> Services (and the TS Services Licensing Server) and reboot
> >> >> the server. You don't install any applications at this
> >> >> stage.
> >> >>
> >> >> When the TS role is installed, it is time to install the
> >> >> user applications again. This must be done when the TS is in
> >> >> "install mode", but that mode has nothing to do with the
> >> >> installation of the TS role.
> >> >>
> >> >> Install mode is a special TS operational mode, in which the
> >> >> server monitors all changes made by the application's
> >> >> install program to the registry and the file system. It
> >> >> stores a copy of all these changes in a special area of the
> >> >> registry, known as the "shadow area". When the installation
> >> >> of the application is finished, you put the server back into
> >> >> its normal operational mode, which is called "execute mode".
> >> >> You put the server into install mode by typing "change user
> >> >> /install" (without the quotes) at a command line, and put it
> >> >> back into execute mode again by typing "change user
> >> >> /execute". When a user logs on to the Terminal Server with a
> >> >> Remote Desktop client, the server automatically copies the
> >> >> changes made to the server during application installation
> >> >> from the shadow area into the user portion of the registry.
> >> >> This process makes sure that all users get their own
> >> >> personal settings. If you later on need to install another
> >> >> user application, you go through the same process with
> >> >> install mode again. Note that *no* users should be connected
> >> >> to the TS while it is in install mode!
> >> >>
> >> >> Recommended reading:
> >> >>
> >> >> 186498 - Terminal Server Application Integration Information
> >> >> http://support.microsoft.com/?kbid=186498
> >> >>
> >> >> Applications : QuickBooks
> >> >> http://ts.veranoest.net/ts_apps_qb.htm
> >> >>
> >> >> _________________________________________________________
> >> >> Vera Noest
> >> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> >> TS troubleshooting: http://ts.veranoest.net
> >> >> ___ please respond in newsgroup, NOT by private email ___
> >> >>
> >> >> =?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com> wrote
> >> >> on 07 okt 2007 in
> >> >> microsoft.public.windows.terminal_services:
> >> >>
> >> >> > Thank you Vera,
> >> >> >
> >> >> > I understood 99% (yeah right). This is shoulda coulda,
> >> >> > woulda
> >> >> >
> >> >> > There is 1 Server. It will run 1 major multi user
> >> >> > program.( and Probably a New MS Office) No 2nd server.
> >> >> >
> >> >> > So I am guessing here that I leave the roles that are
> >> >> > turned on?? ON?
> >> >> >
> >> >> > 2nd I must uninstall Office, and Quickbooks, and
> >> >> > re-install them during the install mode of Terminal
> >> >> > Services. The data files and .docs, .xls do they remain
> >> >> > in the Server? Or should I make a back up and drop them
> >> >> > back in after the install?
> >> >> >
> >> >> > This statement: that programs must be installed during the
> >> >> > TS install mode to be multi user!!! Is that to say that
> >> >> > AFTER I have the TS running with 5 Cals, I can not place a
> >> >> > NEW Muli-User Program in the system.?
> >> >> >
> >> >> > Everything I am doing here revolves around this: Right now
> >> >> > we only can get to access' to the Server at one time. TS
> >> >> > will allow more based on Cals. We need 5-10 and I will buy
> >> >> > them as we go.
> >> >> >
> >> >> > The Big Program is going to be remotely uploaded from the
> >> >> > seller company. Can this be done "during" TS install mode.
> >> >> > Or can I have them do it After?
> >> >> >
> >> >> > Thank you, Thank you...very much
> >> >> >
> >> >> > Mark
> >> >> >
> >> >> > "Vera Noest [MVP]" wrote:
> >> >> >
> >> >> >> It is recommended that a Terminal Server runs on a member
> >> >> >> server in the domain, not on a DC.
> >> >> >> But before you remove any of the roles that the server
> >> >> >> currently has, make sure that you have another server
> >> >> >> which has these roles. You must have a DC, DHCP, DNS and
> >> >> >> possibly a WINS server in your domain, but they don't
> >> >> >> need to (and shouldn't) run on your terminal server.
> >> >> >> If you decide to demote the server to be a member server
> >> >> >> in the domain, remote Desktop access will continue to
> >> >> >> work just as it does now, i.e. you will still have 2
> >> >> >> concurrent connections (+ one to the console of the
> >> >> >> server).
> >> >> >>
> >> >> >> Note that before installing Terminal Services on the
> >> >> >> server, you will need to uninstall all user applications
> >> >> >> from it, then install TS, and then re-install the user
> >> >> >> applications again.
> >> >> >>
> >> >> >> Installing applications on a Terminal server must be done
> >> >> >> while the server is in "install mode", to ensure
> >> >> >> multi-user functionality.
> >> >> >>
> >> >> >> _________________________________________________________
> >> >> >> Vera Noest
> >> >> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> >> >> TS troubleshooting: http://ts.veranoest.net
> >> >> >> ___ please respond in newsgroup, NOT by private email ___
> >> >> >>
> >> >> >> =?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com>
> >> >> >> wrote on 07 okt 2007 in
> >> >> >> microsoft.public.windows.terminal_services:
> >> >> >>
> >> >> >> > Hi and Thanks for helping.
> >> >> >> >
> >> >> >> > We have a W2K3 Server that is accessed by to local PC's
> >> >> >> > and 2 remote PC's Obviously at this point onlt 2 people
> >> >> >> > at a time can be in.
> >> >> >> >
> >> >> >> > We are expanding and I am going to assign the server
> >> >> >> > Terminal Server Role and add 5 CALS.
> >> >> >> >
> >> >> >> > I see that somewhere along installation a few years
> >> >> >> > ago, I gave this server a role of Domain Controll which
> >> >> >> > I see is directly connected to Active Directory.
> >> >> >> >
> >> >> >> > Do I need The Domain Controller Role. All we will be
> >> >> >> > doing is accessing a main software application. NO
> >> >> >> > email, or web hosting at this point.
> >> >> >> >
> >> >> >> > If I turn off Domain Controller to save memory, will
> >> >> >> > the 2 users remote or local, still have normal access
> >> >> >> > to the server until I switch over to Terminal Services.
> >> >> >> >
> >> >> >> > The other roles that I switched on are, Print Server,
> >> >> >> > (but) it's not really going that. there is a printer
> >> >> >> > hooked to it. DNS server??, DHCP Server?? and Wins
> >> >> >> > Server?? Do I need all these on?
> >> >> >> >
> >> >> >> > We have Microsoft Office on the Server and an Avition
> >> >> >> > multi use software program. This is all it does.
> >> >> >> >
> >> >> >> > Can you set me straight a bit? It seems that as time
> >> >> >> > goes by and I do not use this thing I forget all I
> >> >> >> > learned.
> >> >> >> >
> >> >> >> > We are going to want 5 users 3 local and 2 remote to
> >> >> >> > access simo.
> >> >> >> >
> >> >> >> > Thanks.
> >> >> >> >
> >> >> >> > Mark
>

 

[Vera Noest [MVP]]

Re: Do I need my W2K3 Server to be a Domain Controller

Can't answer that, Mark, I've never used Exchange. But I don't
think that the 32 versus 64 bit plays any roll at all, and I
haven't read any reports here about that kind of problems.
Only thing I know regarding TS and Exchange is that you can't run
them on the same server, since you can't run the Outlook client on
the Exchange server.
But you're planning to separate Exchange from TS, so that's OK.
You might want to ask in an exchange newsgroup, though.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com> wrote on 08
okt 2007 in microsoft.public.windows.terminal_services:

> Vera,
> I took your advice and sought some IT help. Actually called MS,
> and they were a big help.
>
> Plan B: is to Get a dual core (4 Gig) Server to run Quantum and
> stick a small 64bit (4 gig) Exchange Server 2007 behind it
> (don't trust Quantum on 64 bits.)
>
> Server "A" will have TS and W2k3 Standard, and Server 2 will
> have Exchange 2007 @ 64 bits).
>
> Is there any conflict that you know of, in accessing mail coming
> from a 64 bit Exchange Server, through to me, Loging into the TS
> in front at 32 bits?
>
> Whew...in advance.
>
>
>
> "Vera Noest [MVP]" wrote:
>
>> OK, for what it's worth: yes, that sounds OK.
>> Keep the domain, which means keep all other roles on the server
>> (DHCP, DNS, etc). The Vista clients will be able to join the
>> domain.
>> All clients, whether part of the domain or not, should be able
>> to rdp into the server (after being upgraded).
>> Good luck!
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> =?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com> wrote on
>> 07 okt 2007 in microsoft.public.windows.terminal_services:
>>
>> > I am going to have help on sight!
>> > I was just looking for confirmation of things I believe I
>> > have learned.
>> >
>> > #1 I keep the domain and make the Server a TS. (get Cals)
>> > #2 Upgrade Vista Home to Business, # 2 PC to Vista Busness or
>> > XP PRO. (They should then network to the domain correct?
>> >
>> > #3 Remove all programs, and Turn on TS. reboot. Install
>> > programs. # 4 continue to remote in form 2 sites.
>> >
>> > Sound normal? or sorta normal. Believe me. I will not just
>> > throw switchs.
>> >
>> > Thanks.
>> >
>> >
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> Mark, I strongly advice you to hire a consultant, so that
>> >> you can describe your business needs in detail and then the
>> >> consultant can propose the best environment.
>> >> I am not prepared to give advice with such far-reaching
>> >> consequences in a newsgroup. The risks that it won't work
>> >> for you are just too high, because I will never get the
>> >> whole picture.
>> >> _________________________________________________________
>> >> Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server
>> >> TS troubleshooting: http://ts.veranoest.net
>> >> ___ please respond in newsgroup, NOT by private email ___
>> >>
>> >> =?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com> wrote
>> >> on 07 okt 2007 in
>> >> microsoft.public.windows.terminal_services:
>> >>
>> >> > Small group. 2 or 3 people in at a time, no more than 5.
>> >> > OK?
>> >> >
>> >> > I'm just not sure we ever needed a domain.... What I had
>> >> > hoped for was local PC's to network with the Server which
>> >> > was running QB2005. Then the problems began.
>> >> >
>> >> > 1. New PC with Vista Home (problems with QB)(can't hook
>> >> > with domain) 2. #2 PC has XP home. (can't hook with
>> >> > domain.
>> >> >
>> >> > Seems like Workgroup could be the answer.
>> >> >
>> >> > No network: So they are remoting in. How dumb! Seems like
>> >> > I kill the domain and make a workgroup, or upgrade the 2
>> >> > OS's to Vista Business and have them network a domain. QB
>> >> > is going away anyway for a system by Quantum.
>> >> >
>> >> > If I remove the domain:
>> >> > Will I still remote in via MSTSC and my login? Will that
>> >> > work as normal. I must have that.
>> >> >
>> >> > Could the vista machine an xp then network with the server
>> >> > workgroup?
>> >> >
>> >> > The MSTSC brings up an IP address to connect to (presently
>> >> > 24.153.139.***). Would that number change on demotion of
>> >> > the domain to workgroup?
>> >> >
>> >> > I know I am over my head, I just don't want to jump in
>> >> > with both feet. I just want to put a toe in 1st.
>> >> >
>> >> > Thank you very very much.
>> >> >
>> >> > Mark
>> >> >
>> >> > "Vera Noest [MVP]" wrote:
>> >> >
>> >> >> OK, I was assuming that you had another server. Let me
>> >> >> rephrase your options:
>> >> >>
>> >> >> If you uninstall the Domain Controller role, you will not
>> >> >> have a domain anymore, nor Active Directory, just a
>> >> >> standalone server in a workgroup. This is such a major
>> >> >> decision, that I cannot advice you on whether to do this
>> >> >> or not. Most likely, you'll want to keep your domain.
>> >> >> That means that you must keep all of the roles that the
>> >> >> server currently has.
>> >> >>
>> >> >> That leaves you with no choice than to install Terminal
>> >> >> Services on your Domain Controller. This is not
>> >> >> recommended, for both security and performance reasons,
>> >> >> but in very small environments, it can be done.
>> >> >>
>> >> >> As I mentioned, you must uninstall all user applications
>> >> >> before you install Terminal Services. Then install
>> >> >> Terminal Services (and the TS Services Licensing Server)
>> >> >> and reboot the server. You don't install any applications
>> >> >> at this stage.
>> >> >>
>> >> >> When the TS role is installed, it is time to install the
>> >> >> user applications again. This must be done when the TS is
>> >> >> in "install mode", but that mode has nothing to do with
>> >> >> the installation of the TS role.
>> >> >>
>> >> >> Install mode is a special TS operational mode, in which
>> >> >> the server monitors all changes made by the application's
>> >> >> install program to the registry and the file system. It
>> >> >> stores a copy of all these changes in a special area of
>> >> >> the registry, known as the "shadow area". When the
>> >> >> installation of the application is finished, you put the
>> >> >> server back into its normal operational mode, which is
>> >> >> called "execute mode". You put the server into install
>> >> >> mode by typing "change user /install" (without the
>> >> >> quotes) at a command line, and put it back into execute
>> >> >> mode again by typing "change user /execute". When a user
>> >> >> logs on to the Terminal Server with a Remote Desktop
>> >> >> client, the server automatically copies the changes made
>> >> >> to the server during application installation from the
>> >> >> shadow area into the user portion of the registry.
>> >> >> This process makes sure that all users get their own
>> >> >> personal settings. If you later on need to install
>> >> >> another user application, you go through the same process
>> >> >> with install mode again. Note that *no* users should be
>> >> >> connected to the TS while it is in install mode!
>> >> >>
>> >> >> Recommended reading:
>> >> >>
>> >> >> 186498 - Terminal Server Application Integration
>> >> >> Information http://support.microsoft.com/?kbid=186498
>> >> >>
>> >> >> Applications : QuickBooks
>> >> >> http://ts.veranoest.net/ts_apps_qb.htm
>> >> >>
>> >> >> _________________________________________________________
>> >> >> Vera Noest
>> >> >> MCSE, CCEA, Microsoft MVP - Terminal Server
>> >> >> TS troubleshooting: http://ts.veranoest.net
>> >> >> ___ please respond in newsgroup, NOT by private email ___
>> >> >>
>> >> >> =?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com>
>> >> >> wrote on 07 okt 2007 in
>> >> >> microsoft.public.windows.terminal_services:
>> >> >>
>> >> >> > Thank you Vera,
>> >> >> >
>> >> >> > I understood 99% (yeah right). This is shoulda coulda,
>> >> >> > woulda
>> >> >> >
>> >> >> > There is 1 Server. It will run 1 major multi user
>> >> >> > program.( and Probably a New MS Office) No 2nd server.
>> >> >> >
>> >> >> > So I am guessing here that I leave the roles that are
>> >> >> > turned on?? ON?
>> >> >> >
>> >> >> > 2nd I must uninstall Office, and Quickbooks, and
>> >> >> > re-install them during the install mode of Terminal
>> >> >> > Services. The data files and .docs, .xls do they
>> >> >> > remain in the Server? Or should I make a back up and
>> >> >> > drop them back in after the install?
>> >> >> >
>> >> >> > This statement: that programs must be installed during
>> >> >> > the TS install mode to be multi user!!! Is that to say
>> >> >> > that AFTER I have the TS running with 5 Cals, I can not
>> >> >> > place a NEW Muli-User Program in the system.?
>> >> >> >
>> >> >> > Everything I am doing here revolves around this: Right
>> >> >> > now we only can get to access' to the Server at one
>> >> >> > time. TS will allow more based on Cals. We need 5-10
>> >> >> > and I will buy them as we go.
>> >> >> >
>> >> >> > The Big Program is going to be remotely uploaded from
>> >> >> > the seller company. Can this be done "during" TS
>> >> >> > install mode. Or can I have them do it After?
>> >> >> >
>> >> >> > Thank you, Thank you...very much
>> >> >> >
>> >> >> > Mark
>> >> >> >
>> >> >> > "Vera Noest [MVP]" wrote:
>> >> >> >
>> >> >> >> It is recommended that a Terminal Server runs on a
>> >> >> >> member server in the domain, not on a DC.
>> >> >> >> But before you remove any of the roles that the server
>> >> >> >> currently has, make sure that you have another server
>> >> >> >> which has these roles. You must have a DC, DHCP, DNS
>> >> >> >> and possibly a WINS server in your domain, but they
>> >> >> >> don't need to (and shouldn't) run on your terminal
>> >> >> >> server. If you decide to demote the server to be a
>> >> >> >> member server in the domain, remote Desktop access
>> >> >> >> will continue to work just as it does now, i.e. you
>> >> >> >> will still have 2 concurrent connections (+ one to the
>> >> >> >> console of the server).
>> >> >> >>
>> >> >> >> Note that before installing Terminal Services on the
>> >> >> >> server, you will need to uninstall all user
>> >> >> >> applications from it, then install TS, and then
>> >> >> >> re-install the user applications again.
>> >> >> >>
>> >> >> >> Installing applications on a Terminal server must be
>> >> >> >> done while the server is in "install mode", to ensure
>> >> >> >> multi-user functionality.
>> >> >> >>
>> >> >> >> _______________________________________________________
>> >> >> >> __ Vera Noest
>> >> >> >> MCSE, CCEA, Microsoft MVP - Terminal Server
>> >> >> >> TS troubleshooting: http://ts.veranoest.net
>> >> >> >> ___ please respond in newsgroup, NOT by private email
>> >> >> >> ___
>> >> >> >>
>> >> >> >> =?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com>
>> >> >> >> wrote on 07 okt 2007 in
>> >> >> >> microsoft.public.windows.terminal_services:
>> >> >> >>
>> >> >> >> > Hi and Thanks for helping.
>> >> >> >> >
>> >> >> >> > We have a W2K3 Server that is accessed by to local
>> >> >> >> > PC's and 2 remote PC's Obviously at this point onlt
>> >> >> >> > 2 people at a time can be in.
>> >> >> >> >
>> >> >> >> > We are expanding and I am going to assign the server
>> >> >> >> > Terminal Server Role and add 5 CALS.
>> >> >> >> >
>> >> >> >> > I see that somewhere along installation a few years
>> >> >> >> > ago, I gave this server a role of Domain Controll
>> >> >> >> > which I see is directly connected to Active
>> >> >> >> > Directory.
>> >> >> >> >
>> >> >> >> > Do I need The Domain Controller Role. All we will be
>> >> >> >> > doing is accessing a main software application. NO
>> >> >> >> > email, or web hosting at this point.
>> >> >> >> >
>> >> >> >> > If I turn off Domain Controller to save memory, will
>> >> >> >> > the 2 users remote or local, still have normal
>> >> >> >> > access to the server until I switch over to Terminal
>> >> >> >> > Services.
>> >> >> >> >
>> >> >> >> > The other roles that I switched on are, Print
>> >> >> >> > Server, (but) it's not really going that. there is a
>> >> >> >> > printer hooked to it. DNS server??, DHCP Server??
>> >> >> >> > and Wins Server?? Do I need all these on?
>> >> >> >> >
>> >> >> >> > We have Microsoft Office on the Server and an
>> >> >> >> > Avition multi use software program. This is all it
>> >> >> >> > does.
>> >> >> >> >
>> >> >> >> > Can you set me straight a bit? It seems that as time
>> >> >> >> > goes by and I do not use this thing I forget all I
>> >> >> >> > learned.
>> >> >> >> >
>> >> >> >> > We are going to want 5 users 3 local and 2 remote to
>> >> >> >> > access simo.
>> >> >> >> >
>> >> >> >> > Thanks.
>> >> >> >> >
>> >> >> >> > Mark

 

[TP]

Re: Do I need my W2K3 Server to be a Domain Controller

Hi Mark,

For such a small number of users it is more cost effective to
use an Exchange hosting provider. The cost is generally about
$10 per mailbox per month and you can be up and running
in minutes to hours with no up front hardware/software costs.

Compare this to purchasing appropriate server hardware,
2003 server license, exchange licenses, backup software license,
ups, anti-spam licenses, anti-virus licenses, consultant to set up
and maintain, etc. If you do choose to run Exchange 2007
in house I would recommend you get Exchange Standard Edition
with Exchange Standard & Enterprise CALs and purchase
Software Assurance on the Enterprise CALs. That way you
will have Antivirus/Antispam software with updates for the
contract period and the option to use Hosted Filtering/Antivirus/Antispam.

You can run Outlook 2007 on your TS to connect to your
internal Exchange 2007 server or a hosted Exchange server.

-TP

Mark wrote:
> Vera,
> I took your advice and sought some IT help. Actually called MS, and
> they were a big help.
>
> Plan B: is to Get a dual core (4 Gig) Server to run Quantum and stick
> a small 64bit (4 gig) Exchange Server 2007 behind it (don't trust
> Quantum on 64 bits.)
>
> Server "A" will have TS and W2k3 Standard, and Server 2 will have
> Exchange 2007 @ 64 bits).
>
> Is there any conflict that you know of, in accessing mail coming from
> a 64 bit Exchange Server, through to me, Loging into the TS in front
> at 32 bits?
>
> Whew...in advance.

 

[Mark]

Re: Do I need my W2K3 Server to be a Domain Controller

Lots of great information. I can see that haveing the email hosted is a cheap
way to go. I'm not sure why the company wats to spend 5 years of money
hosting email on one piece of equipment.

Servers just blow my mind.. too much thats too different.

Thanks for all the info.

M

"TP" wrote:

> Hi Mark,
>
> For such a small number of users it is more cost effective to
> use an Exchange hosting provider. The cost is generally about
> $10 per mailbox per month and you can be up and running
> in minutes to hours with no up front hardware/software costs.
>
> Compare this to purchasing appropriate server hardware,
> 2003 server license, exchange licenses, backup software license,
> ups, anti-spam licenses, anti-virus licenses, consultant to set up
> and maintain, etc. If you do choose to run Exchange 2007
> in house I would recommend you get Exchange Standard Edition
> with Exchange Standard & Enterprise CALs and purchase
> Software Assurance on the Enterprise CALs. That way you
> will have Antivirus/Antispam software with updates for the
> contract period and the option to use Hosted Filtering/Antivirus/Antispam.
>
> You can run Outlook 2007 on your TS to connect to your
> internal Exchange 2007 server or a hosted Exchange server.
>
> -TP
>
> Mark wrote:
> > Vera,
> > I took your advice and sought some IT help. Actually called MS, and
> > they were a big help.
> >
> > Plan B: is to Get a dual core (4 Gig) Server to run Quantum and stick
> > a small 64bit (4 gig) Exchange Server 2007 behind it (don't trust
> > Quantum on 64 bits.)
> >
> > Server "A" will have TS and W2k3 Standard, and Server 2 will have
> > Exchange 2007 @ 64 bits).
> >
> > Is there any conflict that you know of, in accessing mail coming from
> > a 64 bit Exchange Server, through to me, Loging into the TS in front
> > at 32 bits?
> >
> > Whew...in advance.
>

 

[Hank Arnold (MVP)]

Re: Do I need my W2K3 Server to be a Domain Controller

Vera Noest [MVP] wrote:

> If you decide to demote the server to be a member server in the
> domain, remote Desktop access will continue to work just as it does
> now, i.e. you will still have 2 concurrent connections (+ one to
> the console of the server).

Vera,

Is it necessary to uninstall the apps? I would have thought that
re-installing the apps would do just fine...

--

Regards,
Hank Arnold
Microsoft MVP
Windows Server - Directory Services

 

[Hank Arnold (MVP)]

Re: Do I need my W2K3 Server to be a Domain Controller

Exchange 2007 *REQUIRES* 64 bit hardware and OS..... (One reason we are
planning to outsource our Exchange 5.5/W2K server)

--

Regards,
Hank Arnold
Microsoft MVP
Windows Server - Directory Services

Vera Noest [MVP] wrote:
> Can't answer that, Mark, I've never used Exchange. But I don't
> think that the 32 versus 64 bit plays any roll at all, and I
> haven't read any reports here about that kind of problems.
> Only thing I know regarding TS and Exchange is that you can't run
> them on the same server, since you can't run the Outlook client on
> the Exchange server.
> But you're planning to separate Exchange from TS, so that's OK.
> You might want to ask in an exchange newsgroup, though.
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com> wrote on 08
> okt 2007 in microsoft.public.windows.terminal_services:
>
>> Vera,
>> I took your advice and sought some IT help. Actually called MS,
>> and they were a big help.
>>
>> Plan B: is to Get a dual core (4 Gig) Server to run Quantum and
>> stick a small 64bit (4 gig) Exchange Server 2007 behind it
>> (don't trust Quantum on 64 bits.)
>>
>> Server "A" will have TS and W2k3 Standard, and Server 2 will
>> have Exchange 2007 @ 64 bits).
>>
>> Is there any conflict that you know of, in accessing mail coming
>> from a 64 bit Exchange Server, through to me, Loging into the TS
>> in front at 32 bits?
>>
>> Whew...in advance.
>>
>>
>>
>> "Vera Noest [MVP]" wrote:
>>
>>> OK, for what it's worth: yes, that sounds OK.
>>> Keep the domain, which means keep all other roles on the server
>>> (DHCP, DNS, etc). The Vista clients will be able to join the
>>> domain.
>>> All clients, whether part of the domain or not, should be able
>>> to rdp into the server (after being upgraded).
>>> Good luck!
>>> _________________________________________________________
>>> Vera Noest
>>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>> TS troubleshooting: http://ts.veranoest.net
>>> ___ please respond in newsgroup, NOT by private email ___
>>>
>>> =?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com> wrote on
>>> 07 okt 2007 in microsoft.public.windows.terminal_services:
>>>
>>>> I am going to have help on sight!
>>>> I was just looking for confirmation of things I believe I
>>>> have learned.
>>>>
>>>> #1 I keep the domain and make the Server a TS. (get Cals)
>>>> #2 Upgrade Vista Home to Business, # 2 PC to Vista Busness or
>>>> XP PRO. (They should then network to the domain correct?
>>>>
>>>> #3 Remove all programs, and Turn on TS. reboot. Install
>>>> programs. # 4 continue to remote in form 2 sites.
>>>>
>>>> Sound normal? or sorta normal. Believe me. I will not just
>>>> throw switchs.
>>>>
>>>> Thanks.
>>>>
>>>>
>>>>
>>>> "Vera Noest [MVP]" wrote:
>>>>
>>>>> Mark, I strongly advice you to hire a consultant, so that
>>>>> you can describe your business needs in detail and then the
>>>>> consultant can propose the best environment.
>>>>> I am not prepared to give advice with such far-reaching
>>>>> consequences in a newsgroup. The risks that it won't work
>>>>> for you are just too high, because I will never get the
>>>>> whole picture.
>>>>> _________________________________________________________
>>>>> Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server
>>>>> TS troubleshooting: http://ts.veranoest.net
>>>>> ___ please respond in newsgroup, NOT by private email ___
>>>>>
>>>>> =?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com> wrote
>>>>> on 07 okt 2007 in
>>>>> microsoft.public.windows.terminal_services:
>>>>>
>>>>>> Small group. 2 or 3 people in at a time, no more than 5.
>>>>>> OK?
>>>>>>
>>>>>> I'm just not sure we ever needed a domain.... What I had
>>>>>> hoped for was local PC's to network with the Server which
>>>>>> was running QB2005. Then the problems began.
>>>>>>
>>>>>> 1. New PC with Vista Home (problems with QB)(can't hook
>>>>>> with domain) 2. #2 PC has XP home. (can't hook with
>>>>>> domain.
>>>>>>
>>>>>> Seems like Workgroup could be the answer.
>>>>>>
>>>>>> No network: So they are remoting in. How dumb! Seems like
>>>>>> I kill the domain and make a workgroup, or upgrade the 2
>>>>>> OS's to Vista Business and have them network a domain. QB
>>>>>> is going away anyway for a system by Quantum.
>>>>>>
>>>>>> If I remove the domain:
>>>>>> Will I still remote in via MSTSC and my login? Will that
>>>>>> work as normal. I must have that.
>>>>>>
>>>>>> Could the vista machine an xp then network with the server
>>>>>> workgroup?
>>>>>>
>>>>>> The MSTSC brings up an IP address to connect to (presently
>>>>>> 24.153.139.***). Would that number change on demotion of
>>>>>> the domain to workgroup?
>>>>>>
>>>>>> I know I am over my head, I just don't want to jump in
>>>>>> with both feet. I just want to put a toe in 1st.
>>>>>>
>>>>>> Thank you very very much.
>>>>>>
>>>>>> Mark
>>>>>>
>>>>>> "Vera Noest [MVP]" wrote:
>>>>>>
>>>>>>> OK, I was assuming that you had another server. Let me
>>>>>>> rephrase your options:
>>>>>>>
>>>>>>> If you uninstall the Domain Controller role, you will not
>>>>>>> have a domain anymore, nor Active Directory, just a
>>>>>>> standalone server in a workgroup. This is such a major
>>>>>>> decision, that I cannot advice you on whether to do this
>>>>>>> or not. Most likely, you'll want to keep your domain.
>>>>>>> That means that you must keep all of the roles that the
>>>>>>> server currently has.
>>>>>>>
>>>>>>> That leaves you with no choice than to install Terminal
>>>>>>> Services on your Domain Controller. This is not
>>>>>>> recommended, for both security and performance reasons,
>>>>>>> but in very small environments, it can be done.
>>>>>>>
>>>>>>> As I mentioned, you must uninstall all user applications
>>>>>>> before you install Terminal Services. Then install
>>>>>>> Terminal Services (and the TS Services Licensing Server)
>>>>>>> and reboot the server. You don't install any applications
>>>>>>> at this stage.
>>>>>>>
>>>>>>> When the TS role is installed, it is time to install the
>>>>>>> user applications again. This must be done when the TS is
>>>>>>> in "install mode", but that mode has nothing to do with
>>>>>>> the installation of the TS role.
>>>>>>>
>>>>>>> Install mode is a special TS operational mode, in which
>>>>>>> the server monitors all changes made by the application's
>>>>>>> install program to the registry and the file system. It
>>>>>>> stores a copy of all these changes in a special area of
>>>>>>> the registry, known as the "shadow area". When the
>>>>>>> installation of the application is finished, you put the
>>>>>>> server back into its normal operational mode, which is
>>>>>>> called "execute mode". You put the server into install
>>>>>>> mode by typing "change user /install" (without the
>>>>>>> quotes) at a command line, and put it back into execute
>>>>>>> mode again by typing "change user /execute". When a user
>>>>>>> logs on to the Terminal Server with a Remote Desktop
>>>>>>> client, the server automatically copies the changes made
>>>>>>> to the server during application installation from the
>>>>>>> shadow area into the user portion of the registry.
>>>>>>> This process makes sure that all users get their own
>>>>>>> personal settings. If you later on need to install
>>>>>>> another user application, you go through the same process
>>>>>>> with install mode again. Note that *no* users should be
>>>>>>> connected to the TS while it is in install mode!
>>>>>>>
>>>>>>> Recommended reading:
>>>>>>>
>>>>>>> 186498 - Terminal Server Application Integration
>>>>>>> Information http://support.microsoft.com/?kbid=186498
>>>>>>>
>>>>>>> Applications : QuickBooks
>>>>>>> http://ts.veranoest.net/ts_apps_qb.htm
>>>>>>>
>>>>>>> _________________________________________________________
>>>>>>> Vera Noest
>>>>>>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>>>>>> TS troubleshooting: http://ts.veranoest.net
>>>>>>> ___ please respond in newsgroup, NOT by private email ___
>>>>>>>
>>>>>>> =?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com>
>>>>>>> wrote on 07 okt 2007 in
>>>>>>> microsoft.public.windows.terminal_services:
>>>>>>>
>>>>>>>> Thank you Vera,
>>>>>>>>
>>>>>>>> I understood 99% (yeah right). This is shoulda coulda,
>>>>>>>> woulda
>>>>>>>>
>>>>>>>> There is 1 Server. It will run 1 major multi user
>>>>>>>> program.( and Probably a New MS Office) No 2nd server.
>>>>>>>>
>>>>>>>> So I am guessing here that I leave the roles that are
>>>>>>>> turned on?? ON?
>>>>>>>>
>>>>>>>> 2nd I must uninstall Office, and Quickbooks, and
>>>>>>>> re-install them during the install mode of Terminal
>>>>>>>> Services. The data files and .docs, .xls do they
>>>>>>>> remain in the Server? Or should I make a back up and
>>>>>>>> drop them back in after the install?
>>>>>>>>
>>>>>>>> This statement: that programs must be installed during
>>>>>>>> the TS install mode to be multi user!!! Is that to say
>>>>>>>> that AFTER I have the TS running with 5 Cals, I can not
>>>>>>>> place a NEW Muli-User Program in the system.?
>>>>>>>>
>>>>>>>> Everything I am doing here revolves around this: Right
>>>>>>>> now we only can get to access' to the Server at one
>>>>>>>> time. TS will allow more based on Cals. We need 5-10
>>>>>>>> and I will buy them as we go.
>>>>>>>>
>>>>>>>> The Big Program is going to be remotely uploaded from
>>>>>>>> the seller company. Can this be done "during" TS
>>>>>>>> install mode. Or can I have them do it After?
>>>>>>>>
>>>>>>>> Thank you, Thank you...very much
>>>>>>>>
>>>>>>>> Mark
>>>>>>>>
>>>>>>>> "Vera Noest [MVP]" wrote:
>>>>>>>>
>>>>>>>>> It is recommended that a Terminal Server runs on a
>>>>>>>>> member server in the domain, not on a DC.
>>>>>>>>> But before you remove any of the roles that the server
>>>>>>>>> currently has, make sure that you have another server
>>>>>>>>> which has these roles. You must have a DC, DHCP, DNS
>>>>>>>>> and possibly a WINS server in your domain, but they
>>>>>>>>> don't need to (and shouldn't) run on your terminal
>>>>>>>>> server. If you decide to demote the server to be a
>>>>>>>>> member server in the domain, remote Desktop access
>>>>>>>>> will continue to work just as it does now, i.e. you
>>>>>>>>> will still have 2 concurrent connections (+ one to the
>>>>>>>>> console of the server).
>>>>>>>>>
>>>>>>>>> Note that before installing Terminal Services on the
>>>>>>>>> server, you will need to uninstall all user
>>>>>>>>> applications from it, then install TS, and then
>>>>>>>>> re-install the user applications again.
>>>>>>>>>
>>>>>>>>> Installing applications on a Terminal server must be
>>>>>>>>> done while the server is in "install mode", to ensure
>>>>>>>>> multi-user functionality.
>>>>>>>>>
>>>>>>>>> _______________________________________________________
>>>>>>>>> __ Vera Noest
>>>>>>>>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>>>>>>>> TS troubleshooting: http://ts.veranoest.net
>>>>>>>>> ___ please respond in newsgroup, NOT by private email
>>>>>>>>> ___
>>>>>>>>>
>>>>>>>>> =?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com>
>>>>>>>>> wrote on 07 okt 2007 in
>>>>>>>>> microsoft.public.windows.terminal_services:
>>>>>>>>>
>>>>>>>>>> Hi and Thanks for helping.
>>>>>>>>>>
>>>>>>>>>> We have a W2K3 Server that is accessed by to local
>>>>>>>>>> PC's and 2 remote PC's Obviously at this point onlt
>>>>>>>>>> 2 people at a time can be in.
>>>>>>>>>>
>>>>>>>>>> We are expanding and I am going to assign the server
>>>>>>>>>> Terminal Server Role and add 5 CALS.
>>>>>>>>>>
>>>>>>>>>> I see that somewhere along installation a few years
>>>>>>>>>> ago, I gave this server a role of Domain Controll
>>>>>>>>>> which I see is directly connected to Active
>>>>>>>>>> Directory.
>>>>>>>>>>
>>>>>>>>>> Do I need The Domain Controller Role. All we will be
>>>>>>>>>> doing is accessing a main software application. NO
>>>>>>>>>> email, or web hosting at this point.
>>>>>>>>>>
>>>>>>>>>> If I turn off Domain Controller to save memory, will
>>>>>>>>>> the 2 users remote or local, still have normal
>>>>>>>>>> access to the server until I switch over to Terminal
>>>>>>>>>> Services.
>>>>>>>>>>
>>>>>>>>>> The other roles that I switched on are, Print
>>>>>>>>>> Server, (but) it's not really going that. there is a
>>>>>>>>>> printer hooked to it. DNS server??, DHCP Server??
>>>>>>>>>> and Wins Server?? Do I need all these on?
>>>>>>>>>>
>>>>>>>>>> We have Microsoft Office on the Server and an
>>>>>>>>>> Avition multi use software program. This is all it
>>>>>>>>>> does.
>>>>>>>>>>
>>>>>>>>>> Can you set me straight a bit? It seems that as time
>>>>>>>>>> goes by and I do not use this thing I forget all I
>>>>>>>>>> learned.
>>>>>>>>>>
>>>>>>>>>> We are going to want 5 users 3 local and 2 remote to
>>>>>>>>>> access simo.
>>>>>>>>>>
>>>>>>>>>> Thanks.
>>>>>>>>>>
>>>>>>>>>> Mark

 

[Hank Arnold (MVP)]

Re: Do I need my W2K3 Server to be a Domain Controller

First off, I'd suggest that if they are willing to spend the kind of
money you are talking about (new 64 bit hardware, OS, CALs, TSCALs
Exchange, etc.), they can spend a few bucks to hire a *real* consultant.
Asking MS to configure things is like having the fox guard the hen house....

You only have 5 people max. Hard to understand the expense & effort with
that small a population. Also, consider the technical support that will
be required. Either you will have to train and pay an admin or pay for
external tech support....

I would seriously consider SBS 2003 (DC, AD, Exchange) for your org and
a second server for Quantum.

Get a real consultant. It will save you a ton of money over what you are
talking here.

--

Regards,
Hank Arnold
Microsoft MVP
Windows Server - Directory Services

Mark wrote:
> Lots of great information. I can see that haveing the email hosted is a cheap
> way to go. I'm not sure why the company wats to spend 5 years of money
> hosting email on one piece of equipment.
>
> Servers just blow my mind.. too much thats too different.
>
> Thanks for all the info.
>
> M
>
> "TP" wrote:
>
>> Hi Mark,
>>
>> For such a small number of users it is more cost effective to
>> use an Exchange hosting provider. The cost is generally about
>> $10 per mailbox per month and you can be up and running
>> in minutes to hours with no up front hardware/software costs.
>>
>> Compare this to purchasing appropriate server hardware,
>> 2003 server license, exchange licenses, backup software license,
>> ups, anti-spam licenses, anti-virus licenses, consultant to set up
>> and maintain, etc. If you do choose to run Exchange 2007
>> in house I would recommend you get Exchange Standard Edition
>> with Exchange Standard & Enterprise CALs and purchase
>> Software Assurance on the Enterprise CALs. That way you
>> will have Antivirus/Antispam software with updates for the
>> contract period and the option to use Hosted Filtering/Antivirus/Antispam.
>>
>> You can run Outlook 2007 on your TS to connect to your
>> internal Exchange 2007 server or a hosted Exchange server.
>>
>> -TP
>>
>> Mark wrote:
>>> Vera,
>>> I took your advice and sought some IT help. Actually called MS, and
>>> they were a big help.
>>>
>>> Plan B: is to Get a dual core (4 Gig) Server to run Quantum and stick
>>> a small 64bit (4 gig) Exchange Server 2007 behind it (don't trust
>>> Quantum on 64 bits.)
>>>
>>> Server "A" will have TS and W2k3 Standard, and Server 2 will have
>>> Exchange 2007 @ 64 bits).
>>>
>>> Is there any conflict that you know of, in accessing mail coming from
>>> a 64 bit Exchange Server, through to me, Loging into the TS in front
>>> at 32 bits?
>>>
>>> Whew...in advance.


--

Regards,
Hank Arnold
Microsoft MVP
Windows Server - Directory Services

 

[Mark]

Re: Do I need my W2K3 Server to be a Domain Controller

just trying to help.

There was a day I didn't know anything about PC either. I am now rather
server savy...

I'm done...Thanks those in the know!

Mark

"Hank Arnold (MVP)" wrote:

> First off, I'd suggest that if they are willing to spend the kind of
> money you are talking about (new 64 bit hardware, OS, CALs, TSCALs
> Exchange, etc.), they can spend a few bucks to hire a *real* consultant.
> Asking MS to configure things is like having the fox guard the hen house....
>
> You only have 5 people max. Hard to understand the expense & effort with
> that small a population. Also, consider the technical support that will
> be required. Either you will have to train and pay an admin or pay for
> external tech support....
>
> I would seriously consider SBS 2003 (DC, AD, Exchange) for your org and
> a second server for Quantum.
>
> Get a real consultant. It will save you a ton of money over what you are
> talking here.
>
> --
>
> Regards,
> Hank Arnold
> Microsoft MVP
> Windows Server - Directory Services
>
> Mark wrote:
> > Lots of great information. I can see that haveing the email hosted is a cheap
> > way to go. I'm not sure why the company wats to spend 5 years of money
> > hosting email on one piece of equipment.
> >
> > Servers just blow my mind.. too much thats too different.
> >
> > Thanks for all the info.
> >
> > M
> >
> > "TP" wrote:
> >
> >> Hi Mark,
> >>
> >> For such a small number of users it is more cost effective to
> >> use an Exchange hosting provider. The cost is generally about
> >> $10 per mailbox per month and you can be up and running
> >> in minutes to hours with no up front hardware/software costs.
> >>
> >> Compare this to purchasing appropriate server hardware,
> >> 2003 server license, exchange licenses, backup software license,
> >> ups, anti-spam licenses, anti-virus licenses, consultant to set up
> >> and maintain, etc. If you do choose to run Exchange 2007
> >> in house I would recommend you get Exchange Standard Edition
> >> with Exchange Standard & Enterprise CALs and purchase
> >> Software Assurance on the Enterprise CALs. That way you
> >> will have Antivirus/Antispam software with updates for the
> >> contract period and the option to use Hosted Filtering/Antivirus/Antispam.
> >>
> >> You can run Outlook 2007 on your TS to connect to your
> >> internal Exchange 2007 server or a hosted Exchange server.
> >>
> >> -TP
> >>
> >> Mark wrote:
> >>> Vera,
> >>> I took your advice and sought some IT help. Actually called MS, and
> >>> they were a big help.
> >>>
> >>> Plan B: is to Get a dual core (4 Gig) Server to run Quantum and stick
> >>> a small 64bit (4 gig) Exchange Server 2007 behind it (don't trust
> >>> Quantum on 64 bits.)
> >>>
> >>> Server "A" will have TS and W2k3 Standard, and Server 2 will have
> >>> Exchange 2007 @ 64 bits).
> >>>
> >>> Is there any conflict that you know of, in accessing mail coming from
> >>> a 64 bit Exchange Server, through to me, Loging into the TS in front
> >>> at 32 bits?
> >>>
> >>> Whew...in advance.
>
>
> --
>
> Regards,
> Hank Arnold
> Microsoft MVP
> Windows Server - Directory Services
>

 

[Vera Noest [MVP]]

Re: Do I need my W2K3 Server to be a Domain Controller

No, you have you remove them completely.
If registry entries made by the installtion procedure are already
presented and thus not made again during re-installation, they will
not be copied to the shadow area in the registry, and thus users
won't get their privare copy of them.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Hank Arnold (MVP)" <rasilon@aol.com> wrote on 11 okt 2007 in
microsoft.public.windows.terminal_services:

> Vera Noest [MVP] wrote:
>
>> If you decide to demote the server to be a member server in the
>> domain, remote Desktop access will continue to work just as it
>> does now, i.e. you will still have 2 concurrent connections (+
>> one to the console of the server).
>
> Vera,
>
> Is it necessary to uninstall the apps? I would have thought that
> re-installing the apps would do just fine...

 

[Vera Noest [MVP]]

Re: Do I need my W2K3 Server to be a Domain Controller

Yes, but does that mean that you cannot connect to it by running
Outlook on a 32-bit system?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Hank Arnold (MVP)" <rasilon@aol.com> wrote on 11 okt 2007 in
microsoft.public.windows.terminal_services:

> Exchange 2007 *REQUIRES* 64 bit hardware and OS..... (One reason
> we are planning to outsource our Exchange 5.5/W2K server)

 

[Mark]

Re: Do I need my W2K3 Server to be a Domain Controller

I took the advisece of you PRO's and called a local IT company. I have the
servers ordered. They understand what I need. They will come out and set us
up...I hope.

I learned alot here. Everyone here is not an expert. I learn when I ask
questions.

Thank you guys very much.

Mark

"Vera Noest [MVP]" wrote:

> No, you have you remove them completely.
> If registry entries made by the installtion procedure are already
> presented and thus not made again during re-installation, they will
> not be copied to the shadow area in the registry, and thus users
> won't get their privare copy of them.
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> "Hank Arnold (MVP)" <rasilon@aol.com> wrote on 11 okt 2007 in
> microsoft.public.windows.terminal_services:
>
> > Vera Noest [MVP] wrote:
> >
> >> If you decide to demote the server to be a member server in the
> >> domain, remote Desktop access will continue to work just as it
> >> does now, i.e. you will still have 2 concurrent connections (+
> >> one to the console of the server).
> >
> > Vera,
> >
> > Is it necessary to uninstall the apps? I would have thought that
> > re-installing the apps would do just fine...
>

 

[Vera Noest [MVP]]

Re: Do I need my W2K3 Server to be a Domain Controller

I think that's a wise decision, Mark.
Make sure that they document what they are doing, and feel free to
get back here if you have any more questions.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?TWFyaw==?= <Mark@discussions.microsoft.com> wrote on 11
okt 2007 in microsoft.public.windows.terminal_services:

> I took the advisece of you PRO's and called a local IT company.
> I have the servers ordered. They understand what I need. They
> will come out and set us up...I hope.
>
> I learned alot here. Everyone here is not an expert. I learn
> when I ask questions.
>
> Thank you guys very much.
>
> Mark
>
> "Vera Noest [MVP]" wrote:
>
>> No, you have you remove them completely.
>> If registry entries made by the installtion procedure are
>> already presented and thus not made again during
>> re-installation, they will not be copied to the shadow area in
>> the registry, and thus users won't get their privare copy of
>> them. _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> "Hank Arnold (MVP)" <rasilon@aol.com> wrote on 11 okt 2007 in
>> microsoft.public.windows.terminal_services:
>>
>> > Vera Noest [MVP] wrote:
>> >
>> >> If you decide to demote the server to be a member server in
>> >> the domain, remote Desktop access will continue to work just
>> >> as it does now, i.e. you will still have 2 concurrent
>> >> connections (+ one to the console of the server).
>> >
>> > Vera,
>> >
>> > Is it necessary to uninstall the apps? I would have thought
>> > that re-installing the apps would do just fine...