We have a Terminal Server at work used to host an Access Application and it also has an IIS application. We are in the process of moving everything from an older machine to a new machine.
The "Technical Owner" of the machine has less server expertise than I do and the last thing I administered was a 2003 Server in 2008 (the year) - UAC recently hit me in the head like a baseball bat. For the most part TS is new to me although I've been aware of it for a long time.
That being said, there are a few things I have seen that are easier / better with Active Directory.
So my question is for a Stand alone Terminal Server, are there any reasons not to run AD?
On the pro list I have...
Group Policy would be nice for some settings but someone did figure out how to set the default user registry settings. In our set it and forget it assumption that works.
Universal groups, so I can put a group within another group.
It feels like there are more than a few things I'm forgetting that are simply easier with AD than stand alone.
On the whole, Google can find a lot more AD solutions to problems than Standalone.
Having never licensed TS personally... Any AD considerations /concerns there?
Any technical reasons not to create a domain?
Devil's advocate - Any tips on doing things standalone vs. AD? I think the big one is the default user registry instead of Group Policy. The other is patience to take the long way (e.g. add users to different groups instead of one and add the group to a group).
The "Technical Owner" of the machine has less server expertise than I do and the last thing I administered was a 2003 Server in 2008 (the year) - UAC recently hit me in the head like a baseball bat. For the most part TS is new to me although I've been aware of it for a long time.
That being said, there are a few things I have seen that are easier / better with Active Directory.
So my question is for a Stand alone Terminal Server, are there any reasons not to run AD?
On the pro list I have...
Group Policy would be nice for some settings but someone did figure out how to set the default user registry settings. In our set it and forget it assumption that works.
Universal groups, so I can put a group within another group.
It feels like there are more than a few things I'm forgetting that are simply easier with AD than stand alone.
On the whole, Google can find a lot more AD solutions to problems than Standalone.
Having never licensed TS personally... Any AD considerations /concerns there?
Any technical reasons not to create a domain?
Devil's advocate - Any tips on doing things standalone vs. AD? I think the big one is the default user registry instead of Group Policy. The other is patience to take the long way (e.g. add users to different groups instead of one and add the group to a group).