Gpresult /v > Gp.txt

This will give you a nice text file on the most import information regrading that single computer.

set devmgr_show_nonpresent_devices=1

Start the device manager

Once you have the device manager open click on the view menu and click “Show Hidden Devices” Now delete or uninstall the orphaned or nonpresent devices. They have a little lighter color than the active devices.

Update: I am using Coldfusion someone said I should try this I am hoping it will help.

First we need to identify the open file you can use lsof (LiSt Open Files) in the console to see what file is open.  But what do you do with that file.

This articular might be able to help. VMware KB

Of course put in your own Server and Share Names in there.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2006834

I tried everything I could think of and the last item on this KB worked for me.

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

Option 3

Add a new disk to the backup schedule by running the wbadmin command from an elevated command prompt.

1.Run the following command from an elevated command prompt to determine the Disk Identifier of the new disk:

wbadmin get disks

2.Based on the output, locate the disk that will be added to the scheduled backup. Make a note of the Disk Identifier. The output will resemble the following:

Disk name: xxxxxxxxxxx

Disk number: x

Disk identifier: {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}

Total space: xxx.xx GB

Used space : xxx.xx GB

3.Run the following command to add the new disk to the Scheduled backup. Use the Disk Identifier from the previous step as the “AddTarget” parameter.

WBADMIN ENABLE BACKUP -addtarget:{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}

4.When you receive the following prompt, type Y for Yes.

“Do you want to enable scheduled backups with the above settings?”

I have been around long enough to remember Novell. My first Novell install was 2.15 far different from anything today. That is when you ran the whole server on 4MB of RAM. Not to say they have completely gone away but look at them now. When Microsoft entered the Server game everyone thought they were wasting their time. Let’s face it Novell had it all raped up. Now look at them. It was not Microsoft that kill Novell it was Novell committed suicide.

The CFO will look at the bottom line. If Microsoft can get them where they need to go for far less money who do you think will win in the long run.

I know I do not want to be running my virtual environment on a Windows platform but that might be the future. Then again there are other players. Maybe it is time to look at Xen. Not because VMware will cost more for my customers it is more will this be the start of a slow death for VMware. I hope not I love this product too much.

So I wanted to reset the search index. The way you do this is start Exchange Management Shell and navigate to this folder. Microsoft\Exchange Server\V14\Scripts Normally here. C:\Program Files\Microsoft\Exchange Server\V14\Scripts You rwill need to do somethig like this with the quotes in place.

cd ‘Program Files\Microsoft\Exchange Server\V14\Scripts’

then run the following command:    .\ResetSearchIndex.ps1 -force -all

MSExchangeSearch service Started

You will get an:
Event ID 109 when the full crawl begins.
Event ID 110 when the full crawl ends.

First I was give a backup file of a WSS 3.0 with the Stsadm utility.

Stsadm -o backup -url http://localhost -filename c:sp_backupsharepoint.bak -overwrit

Then on a new Machine I installed Windows 2008 64-bit and SQL Server 2008 R2 Express 64-bit.

Then I install WSS 3.0 64-Bit and I Created a Site Collection using the same URL of the original server. Then I patched it until it matched the 32-bit WSS 3.0 exactly.

I Configure alternate access mappings to match my backup commend. I was give the backup file without access to the originally Server so I had to match the URL in the originally backup.

Then I restored the backup file with this commend.

stsadm -o restore -url http://localhost -filename C:sp_backupsharepoint.bak -overwrite

Once I had a working site I simply install SharePoint Foundation 2010 and it upgraded the the server. I got a few errors on the upgrade but I am pretty sure they were due to some Custom Web Parts. Except for the custom web parts  everything seems to be working fine.

I do not believe this is a supported way of upgrading but it worked for me I am not sure if it will work for you. I was doing this in a virtual environment so I was able to use snap shots which came in handy.