the ramblings of a crazed IT administrator
Archive for February, 2010
How to Mount a VMware Virtual Disk in Windows
0
Here is handy tool that is part of VMware Workstation, but isnt as well know as some features but can be a real timesaver!
Let’s say your working on a Virtual Machine however it is turned off but you quickly need to pull an important file from it to use or check something you would normally have to go through the process of booting the whole VM to get to the file which may not be desirable if it takes a while to boot the VM, or you dont have the spare RAM (maybe you already have another VM or two running).
Handy Exchange 2003 to Exchange 2010 Guide
31 year ago
Just been reading this guide over at http://msexchangegeek.com and think that anyone who is planning an Exchange 2003 to Exchange 2010 migration should give it a read as it includes some additional steps to take that aren’t included in Microsoft’s Exchange Deployment Tool such as moving the OAB generation to the new server aswell as upgrading the address lists from LDAP filters to OPATH and upgrading Email Address Policies.
Setting up Cacti SNMP Monitoring on a Windows 2003 Server
21 year ago
by Nick
in Windows Server
So this week I’ve been taking a break from planning our Exchange 2010 migration and have been playing around with Cacti as currently we have very little data on things like network and server usage short of a couple of key websites being monitored by an external site to track uptime, but absolutely nothing to tell us if servers are being overloaded or that our internet connection is being saturated.
For those who haven’t heard of Cacti before, its an open-source PHP based frontend that can be used to graph pretty much any data source you can feed it with the most popular source being SNMP which pretty much any business class network enabled bit of electronics supports these days. Even if you only have quite a small network like ours, it can be very useful to actually visualise whats going on, and its a lot easier to show your boss a graph showing how your internet connection is maxed out and needs replacing/upgrading than any other way!
Thank you XKCD
0After a horrible morning of not sleeping, then finally getting to sleep just *after* I turned my alarm off, then missing the train and then finally getting stuck in the queue from hell in the shop round the corner from work I finally got a chance to catch up on yesterdays XKCD comic, if your not already a fan give it a read and you soon will be. Anyway, since sharing is caring, heres yesterdays strip:
How to Restrict Access to Terminal Servers
12 years ago
After finally completing my Group Policy re-write for Windows 7 this week I have gone back to working on the plans for our migration to Exchange 2010. Currently we do use an Exchange 2003 server but only a few users are on it and it is only there to provide compatibility for a couple of specialised programs that are on our Terminal Servers. With the move to Exchange for all users possibly the biggest change will be that now all users have a Windows user account potentially allowing them access to the Terminal Servers when they shouldn’t have any.
In order to do this you could make use of the builtin group called ‘Remote Desktop Users’ which aslong as your using Windows 2003 R2 should have been setup when you installed the Terminal Servers role and by default has permission to connect remotely to any Terminal Server.
It is also possible to customise which users and groups can connect remotely to a Terminal Server so you make your life easier and reuse existing groups to control access, or setup multiple groups if you wanted to limit certain users from connecting to particular Terminal Servers. To do this you can either edit the Local Security Policy on each Terminal Server or apply the changes via Group Policy, the option you are looking for to set this via Group Policy can be seen below (the Local Policy method is also very similar to this and should be easy enough to find):
Enable the 'Allow log on through Remote Desktop Services' Option
Inside this you can add all the users and groups who should have remote access.
While this may seem like all that is needed and while all the users and groups specified can now logon to the Terminal Servers you apply this to you will likely also find that infact *any* user can still login to the Terminal Servers. To correct this we need to make one final change as by default anyone in the Users group can access the server due to the ‘Allow log on locally option’.
Remove the Users group from the 'Allow log on locally' option
While you might be concerned about the warnings given in the ‘Explain this’ tab advising you to not remove users, if you read the relevant section on the link provided it explains that it is safe to do this aslong as you dont remove important users from the list and aslong as users who should have access are granted permission to do so elsewhere.
Hopefully if this has all worked you now have a Terminal Services environment where only those users explicitly allowed can gain access.
