DrT

OK, I admit defeat! Has anyone managed to get remote apps working on 2012? We're just about there except that when the app is launched, the remote computer is untrusted and is using a self-signed certificate, despite a SAN certificate being available. Under Deployment Properties on the server everything is configured for the SAN certificate and shown as "Trusted". We can accept the error and continue but it's messy, especially if a user manages to hit a different VDI each time. I've tried telling it to use the SAN cert from the command line with wmic /namespace:\\root....etc but to no avail. Can it really be this difficult?

Brilliant, thanks. We use Smoothwall so I'll have a look at that.

The problem I'm trying to figure with this is that once a user has entered their credentials for the proxy, they stick. So the next person comes along, and browses using the previous user's credentials. Has anyone solved this yet?

Hi all, I've searched high and low for this and can't believe no one else has had the same problem. Under XP, as administrators, we could view the contents of users' Recent folders. Under Windows 7 the user can view the contents but an administrator can't. We know the files are there from the properties info, but we can't see them. I'm not talking about jump lists or anything shown on the Start Menu - it's purely the contents of the folder at "appdata\microsoft\windows\recent items". Does anyone know what's going on here? Thanks in advance.

Has anyone come across the problem where a right click in the body of an XP logon banner (so the right click context menu displays) prevents a remote shutdown? We are finding that some of our PCs are staying on over night with just a context menu on the screen. A left click anywhere on the desktop allows the shutdown to continue.

We've come across a really strange problem with Previous Versions. I wonder if anyone else has had a similar problem? Briefly, Windows Server 2003, XP client. Loads of disk space on the server. Multiple volumes with all the previous versions held on a separate, non-shadow-copied volume (as per the recommendation). After a period of a couple of weeks, we find we are unable to manipulate large files. For example, when trying to open an Outlook archive file of about 100MB+ we get an "unable to open..." error. Nothing specific to go on. We see similar errors when trying to move or copy other big files. By chance, when we first spotted this, we deleted one Shadow Copy from the server, and the file copy, and Outlook archive worked. Surely a fluke, but no, this is the "fix" - delete one Previous Version, and the problem goes away for a while. Does this sound familiar to anyone?