Few posts ago I wrote about Remote Server Administration Tools, but there was one thing missing from that package, remote management console for Hyper-V. Now Microsoft has released Hyper-V Remote Management console for Windows Vista here are the links:
PS! This should work under Windows 7 as well.
We all know that Exchange Server 2007 is 64-bit only. Is it possible to manage it from 32-bit Windows Vista machine? The answer to this question is yes. There is a 32-bit version of Exchange Management Tools. It includes:
* Exchange Management Console (EMC)
* Exchange Management Shell (EMS)
* Exchange Best Practice Analyzer (ExBPA)
* Exchange Troubleshooting Assistant (ExTRA)
* Help files
Remember these tools require MMC 3.0, the .NET Framework 2.0 and Windows PowerShell. If you don’t have them, you will be prompted to install them. You can run these tools on Windows XP Pro 32-bit edition or Windows Vista 32-bit edition.
I’m not sure if people know this but Microsoft has released Remote Server Administration Tools. RSAT enables to remotely manage Windows Server 2008 roles and features from a computer running Windows Vista SP1. It includes also support for managing Windows Server 2008 Core Edition. Basically it’s “the next version” of ADMINPAK.MSI.
Here are the 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 Service Tools
* DNS Server Service Tools
* Shared Folders Tools
* Network Policy and Access Services Tools
* Terminal Services Tools
* Universal Description, Discovery, and Integration (UDDI) Services Tools
Here are the Feature Administration Tools:
* BitLocker Drive Encryption Tools
* Failover Clustering Tools
* Group Policy Management Tools
* Network Load Balancing Tools
* SMTP Server Tools
* Storage Manager for SANs Tools
* Windows System Resource Manager Tools
It is possible to manage Windows Server 2003 servers as well and here’s the list from the tools:
*Active Directory Domain Services (AD DS) Tools
*Active Directory Lightweight Directory Services (AD LDS) Tools
*Active Directory Certificate Services (AD CS) Tools
*DHCP Server Tools
*DNS Server Tools
*Group Policy Management Tools
*Network Load Balancing Tools
*Terminal Services Tools
*Universal Description, Discovery, and Integration (UDDI) Services Tools
PS! This should work on Windows 7 as well.
A couple of days ago I was having some problems in Vista as I needed to run a program in domain admin rights but I didn’t want to log in as one. So I started looking around for other options. Vista’s runas is a bit different compared to Windows XP. In XP you could choose what account you wanted to use when using runas, but this has changed in Vista. You can only use runas and run stuff as local computer administrator that’s it. There is a way to change that but you will have to adjust local policy for that. Or use this little program, called ShellRunAs. It’s made by Mark Russinovich and Jon Schwartz. Everything you need to know about this program (screenshot, commands and download) you can get from here.
PS! I tested this in Windows 7, and it works there as well.
I found quite annoying to log in to SCE server every time I needed to do something, I decided to install SCE console on my Vista machine. So I got it installed and run it. Typed in the management server address, the admin username and password but got the error message. I started digging around and found nice solution. In order for the remote Essentials console to connect to the Essentials server I needed to import 2 certificates and sort out the user. Here are the steps I took:
1. You need to import the SSL and WSUS Code Signing certificates from the Essentials server to the remote management machine (in my case my Vista computer). So on the Essentials 2007 server browse to the System Center Essentials 2007\Certificate directory and copy the two certificates (WSUSCodeSigningCert.cer and WSUSSSLCert.cer) to your remote management computer.
2. Open the Certificates MMC for the Computer account on the remote management computer.
3. Import both certificates into the Trusted Root Certification Authority Store. Then import only WSUSCodeSigningCert.cerinto the Third Party Publishers and Trusted Publishers stores.
Now I thought its all done and I’m good to go. So I started the System Center Essentials console typed in the management server name, the admin username and password and the application crashed. It seems that SCE remote console somehow crashes if you try to run it like this. So the solution to this problem was the following. I needed to add my ordinary account to SCE management server local administrators group. So next step (number four) is this:
4. On the Essentials 2007 server, open the Local Users and Groups MMC and add the user, you are using to run your remote console on your computer, to administrators group.