I was presenting at SBSC on 10th of April. Attached to this post is my presentation. In it you can hopefully find some useful resources that will help you do the things you do a little faster.

SBSC - 2012.04 - PowerShell

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.

Yesterday I was presenting at SloWUG. Attached to this post is my presentation. In it you can hopefully find some useful resources that will help you do the things you do a little faster.

Brezplacna orodja in administracija.pptx

I tried to publish a sandbox solution on SharePoint Server and was getting error that Sandbox Code service server was not found. I checked in Central Administration and found out, that Microsoft SharePoint Foundation Sandboxed Code Service was running and that SharePoint 2010 User Code Host Service was set to automatic but not running.

In the event logs, I found out, that I have errors in system logs:

• Event Id: 7031, 7034;
• source: Service Control Manager;
• details: The SharePoint 2010 User Code Host service terminated unexpectedly.

I found out, that service account that was running Sandbox code service needs to have access to performance counters on the server. So what you need to do is pretty simple, you need to grant service account access to counters and you can do it by adding service account as a member of local group Performace Monitor Users in Server Manger.

Voila, after adding user to Performace Monitor Users everything works as expected.

So I wanted to change backup location of my Windows Server backups and everytime I wanted to remove or change backups the MMC was crashing.

So I wanted to do it in Windows PowerShell and found out, that by default Windows Powershell does not have module to manage Windows backups.

What you need to do is to add snapin for Windows Backup by typing:

Add-PSSnapin windows.serverbackup

Then you get all the commands that you can find here: http://technet.microsoft.com/en-us/library/ee706683.aspx.

So, to completely remove backups from Windows Server Backups, just type:

Remove-WBPolicy -All

and confirm it with: y.

Now, I can configure new backup set inside Windows Server backup MMC.

voilà

When you're deploying an ASP.NET website that uses the new Routing feature from MVC, you might run into a problem mapping the routes in Integrated mode. The documentation states that using Integrated mode on IIS7 doesn't entail any extra configuration, but in the odd case it does (throwing Error 404 on routed URLs but not .aspx paths), you can open up your web.config file and modify your <system.webServer> / <modules> tag:

<modules>
...
</modules>

... to something like this:

<modules runAllManagedModulesForAllRequests="true">
...
</modules>

Or, if you're not using modules, just put an empty tag within <system.webServer>:

<modules runAllManagedModulesForAllRequests="true" />

That forces IIS7 to always run all loaded web server modules, including URL Routing (inherited from the 4.0 application pool).

Here are step by step instructions I prepared for NTK workshop.

Migracija iz Windows XP na Windows 7 z brezplačnimi Microsoftovimi orodji_v2.xps (628,31 kb)

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

Today I wanted to install SharePoint Administration Toolkit 4.0. Because there was an earlier version of Administration Toolkit installed on that machine, I got an error saying I have to uninstall all previous versions.

I went to Programs and features and clicked on SharePoint Administration Toolkit and there was first surprise, no Uninstall option. Cool I sad to myself. So I Chose Change option and the clicked "Tis feature and all subfeatures will not be available.", which should unintall SharePoint Administration Toolkit. I was so wrong. I got an error.

So the only thing I was able to do was to first uninstall BatchSiteManagerLinks feature via stsadm: stsadm.exe -o uninstallfeature-name BatchSiteManagerLinks

and then go to Programs and features and click on change option and choose "Tis feature and all subfeatures will not be available." and because you already unistalled feature from Central Administration you can leave "No" in the next step. Just click Finish at the end and now you can install SharePoint Administration Toolkit 4.0.

Voilà

Today I've learned something new and quite interesting also – I’ve found solution for a problem which was nagging me almost from the day I first saw Windows XP.
Often I was having problems with old drivers, which were still present somewhere in the system but not in use for a long time. I was trying to figure out how to remove those drivers and usually I ended up doing it manually with help from my good friend google (now www.bing.com). This used to be long and unrewarding process - not anymore.
Solution I’ve found is also available to you at http://support.microsoft.com/kb/315539.
What you have to do is to add new Environment Variable (it can be User or System) devmgr_show_nonpresent_devices with value 1.
Than you can go and open Device Manager. In the View menu select “Show hidden devices”. If you look around your Device Manager you will see some translucent devices – this devices are not present in your system at the moment. By right clicking on any of them and selecting Uninstall you can remove unused drivers for that device.
What's the best part of this trick is the fact that this also apply to Windows Vista, Windows 7, Windows Server 2003,…

P.S.
You can also check my blog at http://jmarkic.spaces.live.com/ for more tips like this.