AWS

All 64bit drivers have to signed. There should be 64bit signed drivers at the manufacturer site. You shouldn't even need the raid driver anyway. Is something not working that you need the raid driver installed?

Any 64bit motherboard will work. Even the older 64bit boards will work.

If the server is set to auto change to DST then the tasks will use the new time. The task will always run at the time set. There is no way that I know of to automate the process to have them run an hour earlier or later as the case may be. You'd have to manually set the time back or forward.

I would go with at least double the ram that you have now. With that many users logged in at one time the ram usage would go through the roof as you are seeing.

You have to turn on wireless network service in server manager > services.

Windows 7 build 7068 has hit the download sites. First Windows 7 x86 was available for download at torrent sites and news this morning is Windows 7 7068 x64 is also now showing up on the torrent sites. The public beta keys will activate these builds. Try this search on Google to find build 7068 download links.

You can't do it that as far as I know.

From the limited info I was able to find it looks like you can set these alerts using server manager in the security > network settings. strange place to put if you ask me.

You have to own the domain unless you sre using a local address such as localhost.localdomain. It would be best to let the server give out IP to the XP boxes that connect.

Try booting from the XP CD and do fdisk /mbr from the command line of the recovery console. If that doesn't work try a repair install.

Check out the tutorial section of the site. You should be able to follow it to create an image backup and then restore it to the new disk.

I beleive this is the thread. http://freepchelp.forum/f9/com-problem-in-ws2008-263.html

There is a thread here that should help you. Do a search for dcom the site and you'll find it.

If you can't activate them more than likely it was activated before on another box. Have you tried calling Microsoft to do activation that way?

One thing about this beta that is different from the Vista beta is the builds are very stable. It almost looks like a complete OS was released when build 7000 was given to us. I haven't run any of the other builds, but, I imagine they rock solid. The RTM should be excellent.

You can join the workgroup computers to the domain if you choose. I prefer doing it that way. Makes your file sharing a little more secure. I have no experience running a domain controller in a VM so I can't offer any comments on that one.

I know I'm a little late in reporting this and in fact have missed a few builds. If you are looking for beta build of Windows 7 then do a search for Windows 7 build 7057. It is available at many torrent sites in both 32bit and 64bit. If you want Windows 7 build 7057 64bit build search for: If you want Windows 7 build 7057 32bit build search for: You should get the links to download these builds at torrent sites. These builds will activate using the product keys that you used to activate build 7000. While you can no longer download build 7000 from Microsoft you can still get keys to install the builds. Get the beta keys at: http://technet.microsoft.com/en-us/evalcenter/dd353205.aspx

It looks like Microsoft has revised the release schedule for Windows 7. Supposedly the latest build, released on March 11TH, is 7061. I am running Build 7000, the only build beta testers have access to and haven't had any problems with it. Unlike the Vista builds we got this is stable enough to run as an everyday OS. I use Windows build 7000 as my main OS. I even have it installed on my new Dell Mini 10. Beta testers will get the the Windows 7 RC build at the end of April with the public getting Windows 7 RC on May 9TH. This is all still speculation at this point and Microsoft hasn't confirmed anything yet. It is starting to look like Windows 7 will be released much earlier than first reports.

Use the server manager. In it you'll find the roll manager to add extras to each roll.

License Server migration is an added feature in Windows Server 2008 R2. In Windows Server 2008 R2, when you right-click on the server name you will see the Manage RDS CALs option. After selecting this, you will see the Manage RDS CALs Wizard to guide you through the migration process. But to migrate Windows Server 2008 license server, you need to follow the same steps as mentioned in the post. The migration of your license server requires three stages. First, you must activate the new license server. Next, you need to deactivate the old server. Lastly, you need to move all the licenses from the old server to the new server. To do this, you will need to contact Microsoft Clearinghouse over the telephone. You should to be prepared with the paperwork for the original TS licenses, as this data needs to be provided to clearinghouse personnel. If the original paperwork is lost, then you need to contact your Microsoft TAM (Technical Account Manager) to obtain copies. To migrate your license server: Step 1: Activate the new license server: Set up the VM guest as a Win2003 TS license server. Open the TS License Manager tool (licmgr.exe) Activate the server by right-clicking on the server name under the All servers node in the left pane and selecting Activate Server. The Activate Server Wizard will open. Click Next. Select Telephone as your connection method and click Next. On the Country or Region Selection page, select your appropriate country and region. The next page will provide you with the License Server ID and the Microsoft Clearinghouse telephone number to call. Write them on a piece of paper but dont make the call yet. You may want to keep the wizard open. Step 2: De-activate the old license server: Open the TS License Manager tool on your old license server. Change the connection method to telephone by right-clicking the server name under the All servers node in the left pane, selecting Properties, and setting the connection method to Telephone. Again right-click the server name under the All servers node in the left pane, select Advanced and then select Deactivate Server. The License Server Deactivation Wizard will open. Click Next. On the License Server Deactivation page, you will be provided with the same clearinghouse phone number and the License Server ID of your old server. Make a note of this License Server ID as you need to provide this to Microsoft Clearinghouse. Call Microsoft Clearinghouse at the number you have noted and give them the product ID of the new license server which you want to activate and of the old license server which you want to deactivate. Once you have given them this information, Microsoft Clearinghouse will provide you with the confirmation code. Enter this code into the License Server Deactivation Wizard when prompted. Step 3: Move each of the license key packs one by one, from the older LS to the new one: On the same call with the clearinghouse, inform them that you also want to migrate the licenses. Open the License Install Wizard on the new license server. Provide the following information to the clearinghouse which they will use to generate the new License Key Pack ID: The license server ID of the old license server Paper work for the original TS licenses [*]Enter the new license key pack ID in the Install License Wizard and complete the License Installation on the new license server. [*]Repeat the same process for migration of all license key packs. Source: Terminal Services Team Blog

Posted on the E7 blog: Read the rest at E7 Blog

No. There is a download for Windows 2008 R2 beta. Try this link to download R2: Windows Server 2008 R2: Resources

See this article I wrote. It is for Windows 2003, but, it the same way you install mysql on Windows 2008. Windows: Installing MYSQL | Admin Reports

No one has been able to find the answer to this problem. There is a couple similiar threads and they all ran into deadends.

Check event viewer. It should give you an idea about what is happening. It could be the power to the server is interupted or could be a program causing the problem.