Jason Yoder, MCT

The following link will take you to the Microsoft article concerning upgrading your XP RDC clients to the Windows 7/Server 2008 R2 compatible version. Take note of the known issues section. The download link for each version is at the bottom. As always, make sure you test before deploying to your clients. http://support.microsoft.com/kb/969084

To set up the senerio for this question. A user had installed a DNS server on a Winodws Server 2008 Server Core installation and was managing it from a graphical interface on another server. When an attempt was made to look at the log files, the user received the error: Unable to complete the operation on “DNS Events”. The file size exceeds the limit allowed and cannot be saved. Upon further investigation, I found that the log file was actually empty. I also noticed that there were no zones configured for this DNS server. Once I created a forward lookup zone, I was able to open up the log.

A common problem with using a client that multiple users log into is that a sensitive document could be stuck in the local print queue. With law suit heavy lawyers running around, you do not want to put your organization at risk. The below procedure will help to mitigate this issue. (Note: The following procedure is performed and tested on Windows 7) This procedure will set up your clients to clear their print queues when a user logs off. This prevents the printer from coming online and printing sensitive information when another user logs on. On your Windows 7 client, click , type Notepad and press Enter . Copy and past the following code: net stop spooler del %systemroot%\system32\spool\printers\*.shd del %systemroot%\system32\spool\printers\*.spl net start spooler Click File \ Save As In the Save as Type: dropdown box, select All FIles . In the File name: box, type C:\DeletePrinJobs.cmd . In a production environment, you may want to put this somewhere other...

In the original implementation of PowerShell, I was very discouraged with the lack of Active Directory support. SUre, you can create user accounts and Organizational units, but it was not easy.  With PowerShell V2, that all changed with the addition on the Active Directory module. For the Microsoft Exam 70-640, I’m seeing a couple of changes. In the Maintaining the Active Directory Environment , I’m seeing PowerShell listed with no mention of the DS commands that are taught in The instructor lead course 6425B.  Here are some tips on how to do the PowerShell equivalent of the DS commands.   DSQuery returns objects out of Active Directory.  With DSQuery you can return information on objects in Active Directory DSGet returns specified attributes of an object. DSMod modifies specified attributes of an object. DSAdd creates an object in the directory. DSMove moves an object to a new container or OU. DSRM removes an object, all multiple objects, from the ...

On a GUI version of Windows, you have this nice graphical way of turning on Remote Desktop. Just open the Server Manager and click Configure Server Manager . Click Configure Remote Dekstop and you see the nice GUI below.     Not so for Server Core.  One nice thing is that with the R2 version, we can do this without called a long, cryptic script. Log into Server Core R2. Type sconfig and press Enter . Press 7 for Remote Desktop and the press Enter . Press E to Enable and then Enter . You now get two options.  With WIndows Vista and WIndows 7, you can connect to a remote desktop session more securely than you could with Windows 200 or XP.  If you are only going to connecting with Windows Vista/7/2008, then select option 1.  If you will be connecting to this remote desktop session with Windows XP, click option 2. When you see the above prompt, then Remote Desktop is enabled.

According to Microsoft’s documentation , you can prevent the transfer of data by using AD RMS to restrict the Print Screen functionality. Here is an excerpt from that documentation: Microsoft Sharepoint is not required to install or use AD RMS. Using AD RMS with Microsoft Sharepoint can provide the following benefits: Helps to prevent an authorized viewer from copying, modifying, printing, faxing, or copying and pasting the content for unauthorized use Helps to prevent an authorized viewer from copying the content by using the Print Screen feature in Microsoft Windows Restricts access to content to a specified period of time, after which users must confirm their credentials and download the content again Helps to enforce corporate policies that govern the use and dissemination of content within your organization For additional information, see Microsoft Office SharePoint Server (MOSS)( http://go.microsoft.com/fwlink/?LinkId=154664 ).

Once you have activated your AD Recycle Bin, you can recover any deleted object from that point forward. To recover a deleted object, open the PowerShell Console with the AD modules. To do this on Server 2008 R2, Click Start \ Active Directory MOdule for Windows PowerShell . First we need to verify that the object is still in the AD Recycle bin. The account we are looking for in this example is User3 . Type the following line in the Windows PowerShell console: Get_ADObject – Filter {DisplayName –like “User*”} – IncludeDeletedObjects We can see the full name of the object that we need to recover, User3 . Now type: Get_ADObject – Filter {DisplayName –eq “User3”} – IncludeDeletedObjects | Restore-ADObject A quick check of Active Directory Users and Computers will show the restored object and all of its properties.