Friday, August 9, 2013

No GUI Boot Screen Splash

What The No Gui Boot Tweak Does :


This tweak disables the display of the bitmap animation on startup.

win7guiboot 

                                  When the Windows 7 operating system is booting up, it displays to the user an animated graphical Windows logo.  Loading and displaying this logo adds a few seconds to the Windows 7 startup time, so disabling it will shave off these seconds.  The downside?  The screen is black while Windows loads, and if users are uncomfortable with that, then it is not a good idea to disable it.

                                   The logo really has no added value or benefit to display other than letting the user know Windows is loading.  If you have tweaked your system to a comfortable level, and you are comfortable not seeing this image anymore, then it is safe to disable.  Personally, it was tougher for me on Windows 7 than their other operating system, mostly because the Windows load GUI was more fun to look at than it’s predecessors.

Disable The Logo GUI Boot On Windows 7 Startup:


1. Select the Windows ‘Start’ button.
2. In the search box, type ‘msconfig’.
3. Scroll up and right click on the program.
4. Select ‘Run As Administrator’.
5. When the system configuration utility is loaded, select the ‘Boot’ tab.
6. Check the box titled ‘No GUI Boot’ at the bottom center of the form.
7. Click ‘Apply’.
8. Select ‘Ok’.
9. Restart your computer.



 


Thursday, August 1, 2013

Hyper-V

Installing the Hyper-V Role

Now, log in using an account with local administrative privileges, and then open the Server manager. In case you aren’t familiar with the Server Manager, it’s the new tool that acts as a centralized management utility for Windows Server 2008. You can access it by entering the ServerManager.msc command at the server’s Run prompt.

When Server Manager opens, right click on the Roles container, and then choose the Add Roles command from the resulting shortcut menu. Windows will now launch the Add Roles Wizard.


You must choose the Hyper-V Role.

At this point, you will see the screen that’s shown in Figure B. Basically, this screen just tells you that you may end up needing to enable virtualization at the BIOS level prior to installing the Hyper-V roll. Some servers require this, and others don’t. The screen also tells you that after installation is complete, you can use the Hyper-V Manager to create and configure your virtual machines. The serene also contains a few links that you can use to access more information about the Hyper-V role.

This screen allows you to access more information about the role that you are installing.

Click Next, and you will be taken to a screen similar to the one that’s shown in Figure C. As you can see in the figure, your virtual machines require virtual networks in order for them to be able to communicate with other network hosts. Essentially, this screen allows you to choose the physical network adapter that you want to bind the virtual network adapter to.


You must bind the virtual network adapter to at least one physical network adapter.

You have the option of choosing multiple network adapters for load balancing, but you also have the option of using a single physical network adapter for all of your virtual machines. When you have made your selection, click Next.

You should now see a screen confirming that you are about to install the Hyper-V role, and warning you that the server may require a reboot after installing the role. Now, just click the Install button to install the role. The actual amount of time that it takes to install the role varies depending on your server’s performance, but the entire process took about 20 seconds on my server.

When the installation process completes, click the Close button, and then click Yes when you are prompted to reboot the server.  When the server reboots, log back into the server and the Server Manager should automatically load and resume the installation process. After about a minute, you should see a message telling you that Hyper-V has installed successfully. Click Close to complete the wizard.


Terminal services

Terminal services manager and Windows 7

I just found out that Terminal services manager does not exist in Windows 7. But fear not, the Remote Desktop Services Manager will do the trick. It is included in the Remote Server Administration Tools for Windows 7, which can be downloaded from here.

After some serious googling, I was also able to figure out how to actually enable the feature, in "Programs and Features", "Turn Windows Features on or off":

Go to "Remote Server Administation Tools", "Role Administration Tools", and enable "Remote Desktop Services Tools".


 There! Now you'll find the Remote Desktop Services Manager in your start menu — and can start kicking out stale remote desktop connections from your servers. :)