Those who follow my blogs will know that I run a Thin Client section of my network - powered by Windows Thin PC (aka Windows 7 lite... it runs NT6.1) with Server 2008 R2.
This post follows http://www.edugeek.net/blogs/thescar...nt-part-2.html and
Last time out on RDS, we set up Single Sign on, so that our users would log onto a Windows Thin PC as themselves, and changed the shell from "explorer.exe" so that instead a Remote Desktop session
Well, I know its been a long time since my last published blog post! The truth is Ive been working on a few for a while now - but just never got round to finishing any of them.
Heres the first of my next batch... a return to an earlier thread of posts, originally related to Printing on Remote Desktop.
First, a bit of background... traditionally, most systems will be set up to map printers via a logon script. The script typically checks a machine name and adds the appropriate
Right... as part of a corporate branding exercise - I have been working on sorting out the email signature front.
Before everyone says it - yes, I know you can do a "sort of solution" on the Exchange server. Im not going to cover that one in this post - as its more designed for Disclaimers. If you want to know more on that - Google "Exchange Transport Rule Disclaimer". Why not Exchange Transport Rules
Back to this post
Updated 18th November 2011 at 10:43 AM by TheScarfedOne
So, regular readers of my blog will know that we run quite an extensive Remote Desktop Environment at my new School. This poses for some interesting issues when dealing with printing - so a rethink on the traditional methods was needed. Traditional Printer Scripting
Lets start at the beginning - with the "old-school" method of printer mappings. Usually, this was achieved with a good old-fashioned batch script, ala Drive Mappings. Not content with
Updated 18th November 2011 at 12:41 AM by TheScarfedOne