ben90

Hi, I am currently testing NAP with NPS using RDS gateway in Server 2008 R2. With NAP turned off, the gateway server works fine, but with NAP on, all clients get evaluated as non nap-capable and the connection is rejected. I have the NAP agent service running on the client and have the RD Gateway enforcement client enabled but still no joy. After digging around the Microsoft site, it seems that nap capability is determined on the client operating system- it doesn't look at whether services are running etc. The client should be nap capable (client is windows 7) as running napstat.exe on it confirms that the service is running etc. Thanks for any help, Ben

We do that but without the RM software. Appdata and favourites get redirected to a folder in the users home drive (appdata is hidden, favourites is visible). The redirections are done in the registry though (still by group policy but not using the interface for folder redirection) because the folder redirection didn't seem to work otherwise. Also avoids problems with the UNC path limitation because it's directed at a drive letter. Users have their own roaming profile stored on the servers but with the group policy setting 'Exclude folders from roaming profile' applied so basically the only thing in the users roaming profile folder is ntuser.dat and its associated files (Less to copy down at logon etc). Desktop and start menu gets redirected to folders on the servers. I've tried lots of different methods for doing this but the one we have currently seems to work best

They certainly do I would agree with what others have said and use the windows 7 group policies to do the printer mappings- they seem much more reliable now. We had a similar problem to yours where the printer mappings would be random (happened on XP as well) and since using the group policies we haven't had any trouble. It's much easier to customise the printer mappings with item level targeting instead of messing around with scripts as well.