How to Activate remotely Remote Desktop Connections, Windows 2003 and Windows 2008


 

For some reason, if you forget to activate the Remote desktop, and the Datacenter is far away, you can easily activate this feature, by doing the following steps.

First you login in one computer or server, in the same domain.

Open Registry, and connect to Network Registry.

After you connect to your server, navigate to the following hive, HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server

 

 Change the REG_DWORD fDenyTSConnections, from 1 to 0.

 

 

 Now you can connect to your server, as Administrator.

 

If for some reason, don´t work after changes, please reboot the server. Open a command prompt and write the following:

 

 shutdown /r /m \\SERVERNAME /f /t 00

Enjoy 🙂.

 

 

 

Advertisements

Static Routing in Windows Server 2008


Static Routing
in Windows Server 2008

We have been using the route command for years. You can configure
static routing in Windows 2008 Server using either the route command or using
the GUI. However, if you use the Windows GUI interface, those routes will not
be listed in the CLI interface, when you type route print. Thus, I
highly recommend that if you are going to use static routing in Windows 2008,
you just use the route command at the windows command prompt.

So let’s look at some examples of how you configure static routing using
the route command:

Show the static routing table

Showing the static routing table is easy, just use the route print
command, as you see in Figure 1 below.

Figure 1: Showing the IP Routing table in Windows Server 2008

In the route print output, the first important thing that you see is the
interface list. Windows Server IP interfaces are labeled with an interface
number. The interface numbers in Figure 1 are 16, 14, 1, 15, 20, and 12. These
interface numbers are used whenever you add or delete routes to the routing
table.

The second important thing in the route print output is the IPv4
Routing Table. This shows us the network destination, network mask, the default
gateway, interface, and metric. This table tells the Windows Server where to
route the traffic.

Add a static route

So how do you add a static route at the command line? The answer is easy-
use the route add command, like this:

route add 1.1.1.0 mask 255.255.255.0 10.0.1.1 if 1


As you see in Figure 2, the results of our route add was an affirmative
“OK!”

Figure 2: Using the route add command in Windows 2008

What was important in the route add command was the network we want to add,
its subnet, the destination/gateway, and the interface for that route.

This writes the persistent route to the following Windows Registry key as a
string value (REG_SZ):

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\

Parameters\PersistentRoutes

Delete a static route
Deleting a route is even easier than adding a route. All you have to do is
to tell route delete the network that you want to remove, as you see in
Figure 3.

Figure 3: Using the route
delete command in Windows 2008

So those are the basics of configuring static routes at the command line.

Disk Management Extend Fails “The parameter is incorrect.”


I have a couple of cluster nodes that I failed to size the C: drive
adequately and began to run out of disk space. No problem! They’re all virtual
machines, so I just need to expand the disks and away I go! Well, I’ve run into
this situation several times since my lab has a lot of machines that I’ve
upgraded over the years and while 15 – 25 GB volumes were fine prior to Windows
2008, it just doesn’t get it now and I like to use 40 GB volumes. That said,
I’ve seen several cases where the virtual disks grow correctly and show up in
the OS correctly, but when you try and use the Windows 2008 disk extend feature
then you get this error from Logical Disk Manager, “The parameter is
incorrect.”

What’s worse is that the Logical Disk Manager sees the volume as 40 GB, while
the file system still only recognizes it as the original size. See the diagram
below where I’ve laid a Windows Explorer view of the C: file system over the
(supposed) 40 GB volume after extending the volume. Weird huh? What’s worse is
that reboots don’t correct the issue. LDM is firm in it’s belief that this
volume is now 40 GB and the File System doesn’t seem to care.

Here’s the work around that I’ve found to correct this situation. Go back
into Logical Disk Manager (Disk Management in Server Manager) and Shrink the
offending volume by 1 MB. After a minute or so, this will revert the volume back
to it’s original size.

Now you can choose to extend it again and all will be right with the world.
Notice in the screen shot below that both the volume and the file system now
agree on the correct sizing.