Showing posts with label Microsoft Windows Server. Show all posts
Showing posts with label Microsoft Windows Server. Show all posts

Sunday, June 21, 2009

Windows Home Server solves three problems for home networks

So now, here comes Windows Home Server, a work group server for a network of 10 computers or less. I've been beta testing it, reading what others are saying about it, and talking to colleagues who are working with it. The early returns are a lot better than I expected. Windows Home Server is trying to solve three problems:

1. Backups
2. File sharing
3. Remote access to files

Shawn MortonIn order to figure out just how well it accomplishes these tasks, I consulted my colleague Shawn Morton (right), the TechRepublic site manager, because Shawn is the most proficient consumer electronics dude that I know, and he has been testing Windows Home Server with live data. Shawn has a serious home network setup with a variety of PCs, an XP Media Center PC, an Xbox 360, Nintendo Wii, and a ton of other stuff that I won't mention, otherwise you'll end up drooling like me.

Installation

"It's super easy to set up," Shawn said. He installed it on an unused PC that he equipped with several removable drive bays so that he could add more storage in the future.

He noted that it definitely felt like a beta install since there were odd Windows Server 2003 screens that popped up and the computer restarted itself 4-5 times in the process. It took about an hour to install, with the setup handling all of the partitioning and other basic steps that are part of a normal Windows installation.

Windows Home Server, Windows Server, Windows server network

File sharing and Backups

"It creates the shares for you," Shawn said, "and it's easy to point non-technical users to them." It is easy because Windows Home Server uses standard names such as "Music" and "Photos" and "Software" for the network file shares, so you don't have to remember any special character strings or drive letters.

Next, Shawn tried out the backups. "The whole automatic backup thing is really cool," he said. "It backs up your whole PC for you. I think most people don't backup, and they worry about the fact that they don't back up."

Shawn ran some backups and the process went smoothly. When I spoke with him, he was still getting ready to test the recovery of one of the backups using his son's PC.

Remote access

One thing that Shawn really liked was the remote access feature, which can be turned on to make the server accessible over the Internet via Microsoft's livenode.com domain.

"Being able to log into your server from anywhere on the Internet is great," Shawn remarked.

Full info here: http://blogs.techrepublic.com.com/hiner/?p=448

Monday, March 9, 2009

Configuring explicit Run As on Windows Server 2008

Default installations of Windows Server 2008 provide the User Account Control (UAC) security component to manage contexts in which applications run. The default configuration is to Run As the logged in user or simply to Run As Administrator. The issues with the latter option are that it does not specify any user name in particular, and it only refers to local administrative permission. Don’t bother pressing [Shift] and needlessly exploring various right-click menus. To get the explicit Run As functionality that you need for best practice permission assignment, you need to go to the SysInternals bag of tricks.

ShellRunas version 1.01 from Sysinternals (which is now part of TechNet) will get the job done. Downloading ShellRunas is straightforward and performing the following one-liner enables the tool:

shellrunas /reg

This command will install the Run As option on the Start Menu for use in the Windows Shell. Figure A shows a Windows Server 2008 server with the Sysinternals tool installed.

Windows server 2008 services

The ShellRunas command can also work without being installed completely for special one-time iterations of the command. Further, it can be uninstalled with the unreg parameter if you want to remove it from certain configurations. Ironically, adding this tool does not modify the existence of the Windows Secondary Logon service, which provides the functionality to use alternate credentials.

Source: http://blogs.techrepublic.com.com/datacenter/?p=557