Jump to content

Recommended Posts

Posted

We've just set up TS and got all the settings how we want except I need to be able to do two things.

 

First - Map shared network areas to a drive letter (as this isn't picked up as part of profile for some reason) : The home area is mapped to N: though as expected.

 

Second - Hide and prevent access to local drives C:, E: and F:

 

Help please

Posted

If you haven't already done so, create a GPO and link it to the OU containing the terminal server. Use loopback policy processing to configure user settings:

Microsoft Corporation

 

You can add a vbscript (or similar) logon script to map drives: Mapping Network Drives - EduGeek.net Wiki

 

To hide drives, configure the settings in the aforementioned GPO with loopback policy processing: Using Group Policy Objects to hide specified drives

 

I've used this printer logon script to handle terminal services sessions.

  • Thanks 1
Posted

If you are sticking your TS computer accounts in with the DC accounts, then yes they will all get the loopback policy, assuming default permissions.

 

I'd advise you to create a new OU with inheritance blocked. You can then link the policies you want/need to this new OU.

I believe it's default for CC3 to have an OU structure of Domain Controllers>Establishments>ABC>Servers - No Inheritance. I created an OU called Terminal Servers within the Servers - No Inheritance OU.

Posted

Ok then, so I was all hunkey dorey with my new TS until I thought "well what if I tweak this"

 

So a test user tries to load up 'Word' for instance (or any other app) and this warning appears

 

Open File - Security Warning

 

The publisher could not be verified - are you sure you want to run this software?

 

Now the user can click 'Run' or 'Cancel' - If 'Run' is clicked the app loads fine. It's just a bit tedious to click everytime - anyway to stop it?

Posted

I think I have had this while I was experimenting with different policy settings.



 

Presumably you are logging on a with a standard CC3 user? Are you running loopback in merge or replace mode?

Posted
I'd recommend Replace. I did try Merge to minimise having duplicate policies (CC3 GPOs and vanilla GPOs), but this incurred significant performance issues.
Posted

Lets say I had a TS in Computers within an OU called 'TS'. This TS had it's own GPO (as recommended) which was set up in merge mode.

 

Why would it apply that GPO to other machines too? The TS is the only machine in the TS folder

Posted

By having it in merge mode, when a CC3 user logs on to terminal server, they will also pick up all the RM user GPOs. I'd recommend Replace mode, it does require a bit more work, but as I mentioned I had problems in Merge mode (specifically on the terminal server).

 

It wouldn't affect other machines if it's only applied to the TS OU. I was a bit confused by this

What would be the problem if I created this GPO and it started replicating to the rest of the CC3 network?
Posted

No problems - thanks for your help

 

I just wanted to make sure before I started tinkering. I've changed one thing (remove search from start) just to check and everything seems to be working fine.

 

Still having problems with the Unknown Publisher - Do you want to run this?

Posted

Ok np, the performance problems I experienced only became apparent when a few concurrent users were on, web browsing was particularly slow. Not sure what was causing it, twas a weird one.

 

Sorry not sure about the unknown publisher issue.

Posted

I've set things up through GPO and works well for me and other tech accounts.

 

Just used a teacher account and some policies are applied where as the generic desktop and drive mappings aren't - is this a common problem?

Posted

It is indeed.

 

As you are probably aware, drive and printer mappings are delivered to the user by a number of RM components installed on a CC3 workstation. Since these are not present on the terminal server, the mapping does not occur.

 

The lack of wallpaper is probably because the wallpaper file isn't installed on the terminal server. I think these are usually in system32\wallpaper?.bmp. These are usually delivered to the workstation via the Wallpaper and Logon Bitmaps package.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...