Tunear Ubuntu 10.10

Receiving WMI configuration error. SQL Server System Configuration cannot be executed

I found this batch file and ran it and it fixed my WMI problems on SQL Server 2005. Copy this into notepad as save as fixwmi.cmd and then from a command line run c:\fixwmi.cmd.

It takes several minutes to complete and at points it appears that it is not running but it is. After it is complete, you see the :END statement start the SQL server installation again and you should be fixed.



FIXWMI.CMD
------------------------

@echo on
cd /d c:\temp
if not exist %windir%\system32\wbem goto TryInstall
cd /d %windir%\system32\wbem
net stop winmgmt
winmgmt /kill
if exist Rep_bak rd Rep_bak /s /q
rename Repository Rep_bak
for %%i in (*.dll) do RegSvr32 -s %%i
for %%i in (*.exe) do call :FixSrv %%i
for %%i in (*.mof,*.mfl) do Mofcomp %%i
net start winmgmt
goto End

:FixSrv
if /I (%1) == (wbemcntl.exe) goto SkipSrv
if /I (%1) == (wbemtest.exe) goto SkipSrv
if /I (%1) == (mofcomp.exe) goto SkipSrv
%1 /RegServer

:SkipSrv
goto End

:TryInstall
if not exist wmicore.exe goto End
wmicore /s
net start winmgmt
:End

El usuario no esta asociado a una conexion SQL server de confianza

Hoy al tratar de hacer una conexion a una base de datos de SQL Server me marco este error: El usuario no esta asociado a una conexion SQL server de confianza.

Esto es porque existen dos tipos de autentificación de cuentas una es con cuentas de Windows y la otra es Mixta (Windows y SQL), para corregirlo tenemos que abrir SQL Server y en el servidor vamos a Propiedades, en la pestaña de Security dentro de Authentication elegimos SQL Server and Windows y aplicamos :)

Instalación de plantillas de aplicaciones para Windows SharePoint Services 3.0

Instalación de plantillas de aplicaciones para Windows SharePoint Services 3.0

File already has an encoding "UTF-8". ESXi

In the vSphere client, select the ESXi server (Not your VM!) and click the 'Configuration' tab on the right.
On the left, under 'Hardware', select 'Storage'. This should show your datastores to the right.


Right-click on the datastore on the right that contains your VM and select 'Browse Datastore...'. This will bring up the Datastore Browser.
Double-click on the ServerName (where ServerName is the name of your server) folder.
Right-click on ServerName.vmx and select 'Download...'. Save it to some temporary spot on your computer.


Open this file in your favorite text editor (I use SciTE. It's awesome, free and multi-platform) that supports Linux text files. (Linux and Windows use different newline characters)
Find the offending line and delete it. It should be something along the lines of: .encoding = "windows-1252"
Save the file.
Back at the Datastore Browser, click on the button that looks like a stack of coins with an up arrow and select 'Upload File...'.
Upload the file you made changes and enjoy a fully functional VM again.

The path is not of a legal form” while installing the Dynamics CRM Outlook client

Error: The path is not of a legal Form, while installing CRM for Outlook 4.0..

Change the following key:
Key: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\
Installer\UserData\S-1-5-18\Products\59DD8CB00184F24E99A62CF4D6109FA\InstallProperties]

Name: InstallLocation
Set the Data value to “C:\Program Files\Microsoft Dynamics CRM”

Chance root passwd in Trixbox

passwd-amp:
-------------------
htpasswd /usr/local/apache/passwd/wwwpasswd wwwadmin

passwd-maint:
---------------------
htpasswd /usr/local/apache/passwd/wwwpasswd maint

passwd-meetme:
------------------------
htpasswd /usr/local/apache/passwd/wwwpasswd meetme

How to cure "Exceeded Tombstone life"

Made a registry entry which removed the servers error protection. I then replicated to a good server, and removed the registry entry. I did this on both servers and they're both working fine.

In the registry, add an entry.
Go to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters

And add the dword:
Allow Replication With Divergent and Corrupt Partner

Set the value to 1

IP subnetting made easy

IP subnetting is a fundamental subject that’s critical for any IP network engineer to understand, yet students have traditionally had a difficult time grasping it. Over the years, I’ve watched students needlessly struggle through school and in practice when dealing with subnetting because it was never explained to them in an easy-to-understand way. I’ve helped countless individuals learn what subnetting is all about using my own graphical approach and calculator shortcuts, and I’ve put all that experience into this article.
IP addresses and subnets

Although IP stands for Internet Protocol, it’s a communications protocol used from the smallest private network to the massive global Internet. An IP address is a unique identifier given to a single device on an IP network. The IP address consists of a 32-bit number that ranges from 0 to 4294967295. This means that theoretically, the Internet can contain approximately 4.3 billion unique objects. But to make such a large address block easier to handle, it was chopped up into four 8-bit numbers, or “octets,” separated by a period. Instead of 32 binary base-2 digits, which would be too long to read, it’s converted to four base-256 digits. Octets are made up of numbers ranging from 0 to 255. The numbers below show how IP addresses increment.

0.0.0.0
0.0.0.1
...increment 252 hosts...
0.0.0.254
0.0.0.255
0.0.1.0
0.0.1.1
...increment 252 hosts...
0.0.1.254
0.0.1.255
0.0.2.0
0.0.2.1
...increment 4+ billion hosts...
255.255.255.255

The word subnet is short for sub network–a smaller network within a larger one. The smallest subnet that has no more subdivisions within it is considered a single “broadcast domain,” which directly correlates to a single LAN (local area network) segment on an Ethernet switch. The broadcast domain serves an important function because this is where devices on a network communicate directly with each other’s MAC addresses, which don’t route across multiple subnets, let alone the entire Internet. MAC address communications are limited to a smaller network because they rely on ARP broadcasting to find their way around, and broadcasting can be scaled only so much before the amount of broadcast traffic brings down the entire network with sheer broadcast noise. For this reason, the most common smallest subnet is 8 bits, or precisely a single octet, although it can be smaller or slightly larger.

Subnets have a beginning and an ending, and the beginning number is always even and the ending number is always odd. The beginning number is the “Network ID” and the ending number is the “Broadcast ID.” You’re not allowed to use these numbers because they both have special meaning with special purposes. The Network ID is the official designation for a particular subnet, and the ending number is the broadcast address that every device on a subnet listens to. Anytime you want to refer to a subnet, you point to its Network ID and its subnet mask, which defines its size. Anytime you want to send data to everyone on the subnet (such as a multicast), you send it to the Broadcast ID. Later in this article, I’ll show you an easy mathematical and graphical way to determine the Network and Broadcast IDs.
The graphical subnet ruler

Over the years, as I watched people struggle with the subject of IP subnetting, I wanted a better way to teach the subject. I soon realized that many students in IT lacked the necessary background in mathematics and had a hard time with the concept of binary numbers. To help close this gap, I came up with the graphical method of illustrating subnets shown in Figure A. In this example, we’re looking at a range of IP addresses from 10.0.0.0 up to 10.0.32.0. Note that the ending IP of 10.0.32.0 itself is actually the beginning of the next subnet. This network range ends at the number right before it, which is 10.0.31.255.
Figure A

Note that for every bit increase, the size of the subnet doubles in length, along with the number of hosts. The smallest tick mark represents 8 bits, which contains a subnet with 256 hosts–but since you can’t use the first and last IP addresses, there are actually only 254 usable hosts on the network. The easiest way to compute how many usable hosts are in a subnet is to raise 2 to the power of the bit size minus 2. Go up to 9 bits ,and we’re up to 510 usable hosts, because 2 to the 9th is 512, and we don’t count the beginning and ending. Keep on going all the way up to 13 bits, and we’re up to 8,190 usable hosts for the entire ruler shown above.
Learning to properly chop subnets

Subnets can be subdivided into smaller subnets and even smaller ones still. The most important thing to know about chopping up a network is that you can’t arbitrarily pick the beginning and ending. The chopping must be along clean binary divisions. The best way to learn this is to look at my subnet ruler and see what’s a valid subnet. In Figure B, green subnets are valid and red subnets are not.
Figure B

The ruler was constructed like any other ruler, where we mark it down the middle and bisect it. Then, we bisect the remaining sections and with shrinking markers every time we start a new round of bisecting. In the sample above, there were five rounds of bisections. If you look carefully at the edge of any valid (green) subnet blocks, you’ll notice that none of the markers contained within the subnet is higher than the edge’s markers. There is a mathematical reason for this, which we’ll illustrate later, but seeing it graphically will make the math easier to understand.
The role of the subnet mask

The subnet mask plays a crucial role in defining the size of a subnet. Take a look at Figure C. Notice the pattern and pay special attention to the numbers in red. Whenever you’re dealing with subnets, it will come in handy to remember eight special numbers that reoccur when dealing with subnet masks. They are 255, 254, 252, 248, 240, 224, 192, and 128. You’ll see these numbers over and over again in IP networking, and memorizing them will make your life much easier.
Figure C

I’ve included three class sizes. You’ll see the first two classes, with host bit length from 0 to 16, most often. It’s common for DSL and T1 IP blocks to be in the 0- to 8-bit range. Private networks typically work in the 8- to 24-bit range.

Note how the binary mask has all those zeros growing from right to left. The subnet mask in binary form always has all ones to the left and all zeros to the right. The number of zeros is identical to the subnet length. I showed only the portion of the binary subnet in the octet that’s interesting, since all octets to the right consist of zeros and all octets to the left consist of ones. So if we look at the subnet mask where the subnet length is 11 bits long, the full binary subnet mask is 11111111.11111111.11111000.00000000. As you can see under mask octet, the subnet mask transitions from 1 to 0 in the third octet. The particular binary subnet mask translates directly to base-256 form as 255.255.248.0.
The “mask” in subnet mask

The subnet mask not only determines the size of a subnet, but it can also help you pinpoint where the end points on the subnet are if you’re given any IP address within that subnet. The reason it’s called a subnet “mask” is that it literally masks out the host bits and leaves only the Network ID that begins the subnet. Once you know the beginning of the subnet and how big it is, you can determine the end of the subnet, which is the Broadcast ID.

To calculate the Network ID, you simply take any IP address within that subnet and run the AND operator on the subnet mask. Let’s take an IP address of 10.20.237.15 and a subnet mask of 255.255.248.0. Note that this can be and often is written in shorthand as 10.20.237.15/21 because the subnet mask length is 21. Figure D and Figure E show the Decimal and Binary versions of the AND operation.
Figure D
Decimal math
Figure E
Binary math

The binary version shows how the 0s act as a mask on the IP address on top. Inside the masking box, the 0s convert all numbers on top into zeros, no matter what the number is. When you take the resultant binary Network ID and convert it to decimal, you get 10.20.232.0 as the Network ID.

One thing that’s always bothered me about the way subnetting is taught is that students are not shown a simple trick to bypass the need for binary conversions when doing AND operations. I even see IT people in the field using this slow and cumbersome technique to convert everything to binary, run the AND operation, and then convert back to decimal using the Windows Calculator. But there’s a really simple shortcut using the Windows Calculator, since the AND operator works directly on decimal numbers. Simply punch in 237, hit the AND operator, and then 248 and [Enter] to instantly get 232, as shown in Figure F. I’ll never understand why this isn’t explained to students, because it makes mask calculations a lot easier.
Figure F

Since there are 11 zeros in the subnet mask, the subnet is 11 bits long. This means there are 2^11, or 2,048, maximum hosts in the subnet and the last IP in this subnet is 10.20.239.255. You could compute this quickly by seeing there are three zeros in the third octet, which means the third octet of the IP address can have a variance of 2^3, or 8. So the next subnet starts at 10.20.232+8.0, which is 10.20.240.0. If we decrease that by 1, we have 10.20.239.255, which is where this subnet ends. To help you visualize this, Figure G shows it on my subnet ruler.
Figure G
IP classes made simple

For an arbitrary classification of IP subnets, the creators of the Internet chose to break the Internet into multiple classes. Note that these aren’t important as far as your subnet calculations are concerned; this is just how the Internet is “laid out.” The Internet is laid out as Class A, B, C, D, and E. Class A uses up the first half of the entire Internet, Class B uses half of the remaining half, Class C uses the remaining half again, Class D (Multicasting) uses up the remaining half again, and whatever is left over is reserved for Class E. I’ve had students tell me that they struggled with the memorization of IP classes for weeks until they saw this simple table shown in Figure H. This is because you don’t actually need to memorize anything, you just learn the technique for constructing the ruler using half of what’s available.
Figure H

Remember that all subnets start with EVEN numbers and all subnet endings are ODD. Note that 0.0.0.0/8 (0.0.0.0 to 0.255.255.255) isn’t used and 127.0.0.0/8 (127.0.0.0 to 127.255.255.255) is reserved for loopback addresses.

All Class A addresses have their first octet between 1 to 126 because 0 and 127 are reserved. Class A subnets are all 24 bits long, which means the subnet mask is only 8 bits long. For example, we have the entire 3.0.0.0/8 subnet owned by GE, since GE was lucky enough to get in early to be assigned 16.8 million addresses. The U.S. Army owns 6.0.0.0/8. Level 3 Communications owns 8.0.0.0/8. IBM owns 9.0.0.0/8. AT&T owns 12.0.0.0/8. Xerox owns 13.0.0.0/8. HP owns 15.0.0.0/8 and 16.0.0.0/8. Apple owns 17.0.0.0/8.

All Class B addresses have their first octet between 128 and 191. Class B subnets are all 16 bits long, which means the subnet masks are 16 bits long. For example, BBN Communications owns 128.1.0.0/16, which is 128.1.0.0 to 128.1.255.255. Carnegie Mellon University owns 128.2.0.0/16.

All Class C addresses have their first octet between 192 and 223. Class C subnets are all 8 bits long, so the subnet mask is only 24 bits long. Note that ARIN (the organization that assigns Internet addresses) will sell blocks of four Class C addresses only to individual companies and you have to really justify why you need 1,024 Public IP addresses. If you need to run BGP so you can use multiple ISPs for redundancy, you have to have your own block of IP addresses. Also note that this isn’t the old days, where blocks of 16.8 million Class A addresses were handed out for basically nothing. You have to pay an annual fee for your block of 1,024 addresses with a subnet mask of /22, or 255.255.252.0.

The concept of subnet classes can cause harm in actual practice. I’ve actually seen people forget to turn classes off in their old Cisco router and watch large subnet routes get hijacked on a large WAN configured for dynamic routing whenever some routes were added. This is because a Cisco router will assume the subnet mask is the full /8 or /16 or /24 even if you define something in between. All newer Cisco IOS software versions turn off the concept of subnet classes and uses classless routing by default. This is done with the default command “IP Classless.”
Public versus private IP addresses

Besides the reserved IP addresses (0.0.0.0/8 and 127.0.0.0/8) mentioned above, there are other addresses not used on the public Internet. These private subnets consist of private IP addresses and are usually behind a firewall or router that performs NAT (network address translation). NAT is needed because private IP addresses are nonroutable on the public Internet, so they must be translated into public IP addresses before they touch the Internet. Private IPs are never routed because no one really owns them. And since anyone can use them, there’s no right place to point a private IP address to on the public Internet. Private IP addresses are used in most LAN and WAN environments, unless you’re lucky enough to own a Class A or at least a Class B block of addresses, in which case you might have enough IPs to assign internal and external IP addresses.

The following blocks of IP addresses are allocated for private networks:

* 10.0.0.0/8 (10.0.0.0 to 10.255.255.255)
* 172.16.0.0/12 (172.16.0.0 to 172.31.255.255)
* 192.168.0.0/16 (192.168.0.0 to 192.168.255.255)
* 169.254.0.0/16 (169.254.0.0 to 169.254.255.255)*

*Note that 169.254.0.0/16 is a block of private IP addresses used for random self IP assignment where DHCP servers are not available.

10.0.0.0/8 is normally used for larger networks, since there are approximately 16.8 million IP addresses available within that block. They chop it up into lots of smaller groups of subnets for each geographic location, which are then subdivided into even smaller subnets. Smaller companies typically use the 172.16.0.0/12 range, chopped up into smaller subnets, although there’s no reason they can’t use 10.0.0.0/8 if they want to. Home networks typically use a /24 subnet within the 192.168.0.0/16 subnet.

The use of private IP addresses and NAT has prolonged the life of IPv4 for the foreseeable future because it effectively allows a single public IP address to represent thousands of private IP addresses. At the current rate that IPv4 addresses are handed out, we have enough IPv4 addresses for approximately 17 years. ARIN is much more stingy now about handing them out, and small blocks of IP addresses are relatively expensive compared to the old days, when companies like Apple were simply handed a block of 16.8 million addresses. The next version of IP addresses, called IPv6, is 128 bits long–and there are more than 79 thousand trillion trillion times more IP addresses than IPv4. Even if you assigned 4.3 billion people on the planet with 4.3 billion IP addresses each, you would still have more than 18 million trillion IPv6 addresses left!

Comandos (Run) para Windows

Accessibility Controls access.cpl
Add Hardware Wizard hdwwiz.cpl
Add/Remove Programs appwiz.cpl
Administrative Tools control admintools
Automatic Updates wuaucpl.cpl
Bluetooth Transfer Wizard fsquirt
Calculator calc
Certificate Manager certmgr.msc
Character Map charmap
Check Disk Utility chkdsk
Clipboard Viewer clipbrd
Command Prompt cmd
Component Services dcomcnfg
Computer Management compmgmt.msc
Time & Date timedate.cpl
Device Manager devmgmt.msc
Direct X Control Panel (If Installed)* directx.cpl
Direct X Troubleshooter dxdiag
Disk Cleanup Utility cleanmgr
Disk Defragment dfrg.msc
Disk Management diskmgmt.msc
Disk Partition Manager diskpart
Display Properties control desktop
Display Properties desk.cpl
Display Properties (w/Appearance Tab Preselected) control color
Dr. Watson System Troubleshooting Utility drwtsn32
Driver Verifier Utility verifier
Event Viewer eventvwr.msc
File Signature Verification Tool sigverif
Findfast findfast.cpl
Folders Properties control folders
Fonts control fonts
Fonts Folder fonts
Group Policy Editor (XP Prof) gpedit.msc
Internet Properties inetcpl.cpl
IP Configuration (Display Connection Configuration) ipconfig /all
IP Configuration (Display DNS Cache Contents) ipconfig /displaydns
Java Control Panel (If Installed) javaws
Keyboard Properties control keyboard
Local Security Settings secpol.msc
Local Users and Groups lusrmgr.msc
Logs You Out Of Windows logoff
Mouse Properties control mouse
Mouse Properties main.cpl
Network Connections control netconnections
Network Connections ncpa.cpl
Network Setup Wizard netsetup.cpl
Notepad notepad
Nview Desktop Manager (If Installed) nvtuicpl.cpl
ODBC Data Source Administrator odbccp32.cpl
Performance Monitor perfmon.msc
Performance Monitor perfmon
Power Configuration powercfg.cpl
Printers and Faxes control printers
Regional Settings intl.cpl
Registry Editor regedit
Remote Desktop mstsc
Removable Storage ntmsmgr.msc
Removable Storage Operator Requests ntmsoprq.msc
Resultant Set of Policy (XP Prof) rsop.msc
Scanners and Cameras sticpl.cpl
Scheduled Tasks control schedtasks
Security Center wscui.cpl
Services services.msc
Shared Folders fsmgmt.msc
Shuts Down Windows shutdown
Sounds and Audio mmsys.cpl
SQL Client Configuration cliconfg
System Configuration Editor sysedit
System Configuration Utility msconfig
System Properties sysdm.cpl
Task Manager taskmgr
Telnet Client telnet
User Account Management nusrmgr.cpl
Utility Manager utilman
Windows Firewall firewall.cpl
Windows Magnifier magnify
Windows Management Infrastructure wmimgmt.msc
Windows System Security Tool syskey
Windows Update Launches wupdmgr
Windows XP Tour Wizard tourstart
Wordpad write

Compilar programas en Ubuntu

Link necesario para llegar al tutorial de la instalacion de aplicaciones en Ubuntu.

Compact Virtual PC virtual hard disks (.VHDs)

If you use Virtual PC 2007 you know that the virtual hard drive files (.VHDs) can grow quite large. This is due to the fact that .VHD files dynamically expand when software is installed inside the Virtual PC.

After the installation, the original setup files are deleted and no longer take up space in the .VHD, however the .VHD does not dynamically shrink. Once a .VHD file expands - it doesn't shrink.

So here's a HOWTO to shrink the size of a .VHD file:

1) Clean the machine for any temp files etc. - If you're lazy, you can use a program like CCLEANER (http://ccleaner.com), which deletes all temporary files from the Windows installation, Internet Explorer cache, the Recycle Bin, etc.

2) Disable hibernation
If you have hiberation turned on, there's a colossal sized file called hiberfil.sys in the root of the .VHD. Go into Power options in Control Panel and disable hiberation to get rid of this.

3) Capture the Virtual Disk Precompactor .ISO file
In the menu of Virtual PC, capture the Virtual Disk Precompactor .ISO file which is located at: "c:\program files\microsoft virtual pc\virtual machine additions\virtual disk precompactor.iso". The Precompactor should run automatic.

4) Run the VPC2007 Virtual Disk Wizard
Shutdown the Virtual PC and from the Virtual PC console, click File-> Virtual Disk Wizard and "Edit an existing virtual disk". Browse to the .VHD file and select it. Select the "Compact" option and "Replacing the original file". This will take a few minutes depending on the size of your .VHD file.

Host header

Using Host Header Names to Host Multiple Web Sites (IIS 6.0)

Repair/Reset Winsock settings

Most of the Internet connectivity problems arise out of corrupt Winsock settings. Windows sockets settings may get corrupted due to the installation of a networking software, or perhaps due to Malware infestation. You will be able connect to the Internet, but the packets won't transfer back and forth. And errors such as Page cannot be displayed may occur when using Internet Explorer. This article lists the methods (with links to third-party websites) to reset/repair the Winsock configuration to defaults.

Microsoft Knowledgebase articles.

http://support.microsoft.com/?kbid=811259
http://support.microsoft.com/?kbid=817571
http://support.microsoft.com/?kbid=299357


Windows XP Service Pack 2 - New Winsock NETSH commands

Two new Netsh commands are available in Windows XP Service Pack 2.

netsh winsock reset catalog

This command resets the Winsock catalog to the default configuration. This can be useful if a malformed LSP is installed that results in loss of network connectivity. While use of this command can restore network connectivity, it should be used with care because any previously-installed LSPs will need to be re-installed.

netsh winsock show catalog

This command displays the list of Winsock LSPs that are installed on the computer.

To output the results to a file type this in Command Prompt (CMD.EXE)

netsh winsock show catalog >C:\lsp.txt

Cambiarle el nombre a una Maquina Linux

Para cambiar el nombre del pc usamos el comando hostname

* sudo hostname NUEVO_NOMBRE_PC


Editamos el archivo /etc/hostname y reemplazamos el antiguo nombre con el NUEVO_NOMBRE_PC

* sudo gedit /etc/hostname


Editamos el archivo /etc/hosts y en la linea donde aparezca el antiguo nombre ponemos el NUEVO_NOMBRE_PC

* sudo gedit /etc/hosts

How to delete GPT Protective Partition

In Windows XP Professional, if you cannot access or modify GPT disk, you can convert a GPT disk to MBR by using the clean command in DiskPart, which will remove all data and partition structures from the disk.

1. You may see S2VR HD 5 Drives in GPT status.

2. Go to DOS command line (click on “Start Menu”, then “Run”, type in “cmd” in textbox, and hit “OK”)

* Type in “DiskPart” in command line.
* Type in “list disk” in command line to show all disks in this machine.
* Use “select” to set the focus to the specified partition, for example “select disk 1″.
* Use “clean” command to remove GPT disk from the current in-focus disk by zeroing sectors.

3. Go back to Disk Management, you can see all S2VR HD disks are “unallocated” now. Right click on disk info, choose “Initialize Disk”.

4. Choose all drives in S2VR HD and initialize them.

GUI for UBUNTU SERVER EDITION

Its very easy to add GUI for Ubuntu server edition,

U have to follow the following steps for the same,
After installing the Ubuntu server Edition,Login as root by the following command u will get the root previlage,

sudo passwd root

It will ask u the existing password and followed by twice the nex Unix password for the confirmation,

then you have to logout using the command

logout

now u will get the root previlage with
#
prompt,

from there u have to type,

vi /etc/apt/source.list

then uncomment all the lines which ends with "universe",

write it and quit the file

the you have to type the following command,

apt-get install gnome

it will start install the gnome enviornment for you,

followed by

apt-get install ubuntu-desktop
apt-get install KDE

If u needed,

after finishing the download,it will start install the file,

once the same is finished u will get the prompt,

#

from there u type

startx

Now u can see the wonder,Its a GUI OS now,

Extend the 60 day Evaluation of Windows Server 2008

http://support.microsoft.com/kb/948472

Creating Domain Controller on Win Server

Creating the first Windows Server 2003 Domain Controller in a domain

Preface:

One of the greatest features of Windows Server 2003 is its ability to be a Domain Controller (DC). The features of a domain extend further than this tutorial ever could, but some of its most well known features are its ability to store user names and passwords on a central computer (the Domain Controller) or computers (several Domain Controllers). In this tutorial we will cover the "promoting" (or creating) of the first DC in a domain. This will include DNS installation, because without DNS the client computers wouldn't know who the DC is. You can host DNS on a different server, but we'll only deal with the basics.

Method:

Click Start -> Run...

Type "dcpromo" and click "OK"

You will see the first window of the wizard. As it suggests, I suggest reading the help associated with Active Directory. After this, click "Next"

Click "Next" on the compatibility window, and in the next window keep the default option of "Domain Controller for a new domain" selected, and click "Next"

In this tutorial we will create a domain in a new forest, because it is the first DC, so keep that option selected

Now we have to think of a name for our domain. If you own a web domain like "visualwin.com", you can use it, but it isn't suggested because computers inside of your domain may not be able to reach the company website. Active Directory domains don't need to be "real" domains like the one above - they can be anything you wish. So here I will create "visualwin.testdomain"

Now in order to keep things simple, we will use the first part of our domain ("visualwin"), which is the default selection, as the NetBIOS name of the domain

The next dialog suggests storing the AD database and log on separate hard disks, and so do I, but for this tutorial I'll just keep the defaults

The SYSVOL folder is a public share, where things like .MSI software packages can be kept when you will distribute packages (as I said, AD has a lot of different features). Once again, I will keep the default selection but it can be changed if you wish to use the space of another drive

Now we will get a message that basically says that you will need a DNS server in order for everything to work the way we want it (i.e., our "visualwin.testdomain" to be reachable). As I mentioned earlier, we will install the DNS server on this machine as well, but it can be installed elsewhere. So keep the default selection of "Install and configure", and click "Next"

Because, after all, this is a Windows Server 2003 tutorial website, we'll assume there are no pre-Windows 2000 servers that will be accessing this domain, so keep the default of "Permissions compatible only with Windows 2000 or Windows Server 2003 operating systems" and click "Next"

The restore mode password is the single password that all administrators hope to never use, however they should also never forget it because this is the single password that might save a failed server. Make sure it's easy to remember but difficult to guess

Now we will see a summary of what will happen. Make sure it's all correct because changing it afterwards can prove to be difficult

After the previous next was clicked, the actual process occurs. This can take several minutes. It's likely that you will be prompted for your Windows Server 2003 CD (for DNS) so have it handy

If your computer has a dynamically assigned address (from DHCP) you will be prompted to give it a static IP address. Click ok, and then in the Local Area Connection properties, click "Internet Protocol (TCP/IP)" and then "Properties"

In the next window select "Use the following IP address" and select the information that you will use for your domain (and 127.0.0.1 for the primary DNS, because your computer will host DNS. I still suggest setting up an alternate as well.) Click "OK" and then "Close" on the next window

And after a while you will see

Windows XP Login Logout Loop

Problem: The PC (which runs Windows XP with SP2) starts normally. The Windows splash screen appears correctly and then the login prompt correctly loads. You can then enter your user name and password like normal, but as soon as you try to login you are IMMEDIATELY logged back out again. The desktop doesn’t even load. It moves immediately back to the login window where you can then enter your user name and password again. No matter how many times you try to login you always experience this immediate logout. Even if you try to login to the computer in safe mode you still experience the same problem. This problem is documented on Microsoft’s website here.

Solution: I’m sure this behavior can be caused by many different problems, but the most common cause is a virus. If you’re familiar with the Windows registry, this virus changes a few registry key values that makes it impossible to login to your computer. If you’re not familiar with the registry, don’t panic. I’ll post links to a few articles that very clearly explain how to fix this problem. Basically, the virus makes two very simple changes to your computer that render it useless. In order to fix the problem, you have to change these two things back to the way they were while your computer was working.

Easy Fix: The “easy” solution to this problem can be found here. In order to use this fix you have to have your Windows XP install CD. This is the CD that contains the files necessary to install the operating system on your computer. You probably have this disk stashed in a drawer somewhere. You should note that there’s a difference between the Windows XP install CD and the recovery CD that may have shipped with your computer. It’s actually possible that when you bought your computer that it didn’t actually come with a Windows XP install CD. Sometimes computer manufacturers will only ship you a recovery disk, which is altogether different. You need your Windows XP install CD so that you can run an application called the Recovery Console. The link above should provide documentation on how to use the Recovery Console. Unfortunately, this fix didn’t work for John’s computer, but it may work for yours.

Slightly Harder Fix: This fix is the one that ended up working to fix John’s computer. A detailed explanation of this fix can be found here. It requires you to have access to another Windows PC with a CD burner (even if it’s a friend’s computer). You have to download a program called BartPE, which is one of the greatest recovery tools that exists. For this particular problem, BartPE will enable you to quickly change the two settings that the virus messed up. You may need a Windows XP install CD for this method as well. But it may be possible for the program to find what it needs from your friend’s computer without having to have access to this disk.