RSAT Client is the collection of Windows Server management tools which enable IT professionals to manage their Windows Server infrastructure from their PCs running Windows 7 SP1 and Windows 7.

This is the list of Windows Server administration tools which are included in RSAT Client for Win7 SP1:

Server Administration Tools:
Server Manager

Role Administration Tools:
Active Directory Certificate Services (AD CS) Tools
Active Directory Domain Services (AD DS) Tools
Active Directory Lightweight Directory Services (AD LDS) Tools
DHCP Server Tools
DNS Server Tools
File Services Tools
Hyper-V Tools
Terminal Services Tools

Feature Administration Tools:
BitLocker Password Recovery Viewer
Failover Clustering Tools
Group Policy Management Tools
Network Load Balancing Tools
SMTP Server Tools
Storage Explorer Tools
Storage Manager for SANs Tools
Windows System Resource Manager Tools

Download page at Microsoft Download Center: RSAT for Windows 7 with SP1

If you followed my previous post on how to manually install RSAT tools on Windows 7 with SP1 you can also install this update on your PC over existing RSAT tools.

Something probably worth checking out (before you start to deploy SP1):

- Deployment Guide for Windows Server 2008 R2 with SP1 and Windows 7 with SP1
- How to Fix Windows 7 SP1’s “Installation Was not Successful “ Error
- If you are seeing a Fatal error C0000034
- Windows 7 Ultimate SP1 installation fails with error code c0000034
- Windows 7 SP1 fails to install with 0x800f0a13 or 0x800f0826

Yesterday, I was was installing SharePoint Server 2010 at one of our clients and after the install I was getting this errors:

User Profile Service Event ID 1511. It says that account could not log on to the computer and create a profile.

After a little bit of research, I found out that all you have to do is edit a local group policy and than run a cmd and all of these errors are gone.

So run a "gpedit.msc" on your WFE where you are getting these errors and go to Computer Configuration/Windows Settings/Security Settings/Local Policies/User Rights Assigneements and Search for Allow log on Locally

Add the account for which you are getting errors. Then, start command prompt and run a command:

 runas /user:kompas-xnet\sp_apppool cmd

 Type the password and if you go to your users folder you should see a folder with your service account name.

You can now remove Allow log on locally permission for the account. 

Voila.

If you are MCT like me than chances are you already had problems running LAB Launcher on one of your MOC’s. This particular problem appeared with MS Virtual Server 2005 and MS Windows 7. Officially this is not supported configuration but for me this is the only acceptable configuration.
You would ask why… Well, I work at training center and part of my work is to present MOC courses – the other part is administration and engineering of MS technologies. As system engineer I always try to implement new technologies into production. Usually that means my coworkers I are first test dummies. The same goes for all new technologies – not just MS stuff but also network, hardware…
Can you imagine coming on MOC training for Windows 7 and when you enter the classroom there are only Windows XP or Windows Vista systems? What would usually be your first question? Mine would be: Where are all the Windows 7 computers I came to see and work on? And the answer would typically be: “You will be working on Windows 7 systems which are virtualized with MS Virtual Server 2005”. My next logical question would then be: How can you be so self-confident and talk about something if you do not use it by yourself and/or in your environment?
What I’m trying to say is that in our environment I want to have Windows 7 as our main system and when it comes to some particular MOC courses that can be like shooting yourself in your leg and hope for the best. The problem comes with all MOC courses which use Microsoft LAB Launcher. LAB launcher only works with MS Virtual Server 2005 which is not supported on Windows 7. So, do we continue to use pre-Windows 7 systems or we try to find some kind of solution? In my case the answer is: go and find some acceptable solution. So what we need is a workaround for installation and usage of MS Virtual Server 2005 on Windows 7. I’ve tried few different approaches (even some of my own) and the easiest one I was able to find and implement is available in this graphical step-by-step guide.
You can find it at: How to Install Microsoft Virtual Server 2005 R2 with SP1 on Windows 7 (Graphical Step-by-Step)

Source:
Rolly's blog

Silverlight XAP file MIME type is not recognized in IIS6 by default so we have to add it. This can be achieved by following these steps:

'Run As Different User' is implemented with hidden context menu that can be seen by using RightClick+SHIFT key on application icon.

Using only RightClick

Using SHIFT+RightClick

Some time ago I had to set up automatic asr backups in one company. The problem with asr backups is that you need to insert a floopy disk at the end of the backup so that the backup is completed successfuly.

So that was not an option so I was searching again with my best friend google and found out this script:

http://www.unsupportedthoughts.com/automatic_asr/automatic_asr_1.1.html

This gives you an option to fully automate asr backups WITHOUT inserting floppy disk at the end of the backup.

But when everything seemed fine I came accross another issue and that is that i get following errors

So I added the switch /timeout:600 and everything worked fine for some time but then this error again, so I edited the switch /timeout:1000 and now asr backups on all servers are working fine.