When connecting via Remote Desktop to Windows 2008 server it always fails with the following message:
"Your credentials did not work. Your system administrator does not allow the use of saved credentials to log on to the remote computer because its identity is not fully verified. Please enter new credentials."
This error occurs only when I try to go from domain client computer to non-domain server.
In order to fix this you have to do following:
- Log on to your local machine as an administrator.
- Start Group Policy Editor - "gpedit.msc"
- Navigate to "Computer Configuration\Administrative Templates\System\Credentials Delegation".
- Double-click the "Allow Saved Credentials with NTLM-only Server Authentication" policy.
- Enable the policy and then click on the "Show" button to get to the server list.
- Add "TERMSRV/*" to the server list. You can also put their exact server name or for example to enable the setting on all servers in "gsmblog.com" domain you can type "TERMSRV/*.gsmblog.com".
- Confirm the changes by clicking on the "OK" button until you return back to the main Group Policy Object Editor dialog.
- At a command prompt, run "gpupdate" to force the policy to be refreshed immediately on the local machine
If you are looking to transfer an entier DNS Server including Active Directory settings and things like that, you may better use DNSDump.cmd script from here: http://www.reskit.net/DNS/dnsdump.cm_
Just to migrate the zones, simply do following:
1. On the DNS server that is currently hosting the DNS zone(s), change any Active Directory-integrated zones to standard primary. This action creates the zone files that are needed for the destination DNS server.
2. Stop the DNS Server service on both DNS servers.
3. Manually copy the entire contents (subfolders included) of the %SystemRoot%\System32\DNS folder from the source server to the destination server.
4. On the current (old, source) DNS server, start Registry Editor (Regedit.exe).
5. Locate and click the following registry subkey: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\DNS\Zones
6. Export the Zones entry to a registry file.
7. Locate and click the following registry subkey: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\DNS Server\Zones
8. Export the Zones entry to a registry file.
9. On the destination (new) DNS server, double-click each registry file to import the Zones subkeys into the registry.
10. Bring the current DNS server down and transfer its IP address to the destination DNS server.
11. On the destination DNS server, start the DNS Server service. To initiate the registration of the server's A and PTR resource records, run the following command at a command prompt: ipconfig /registerdns
12. If this server is also a domain controller, stop and restart the Net Logon service to register the Service (SRV) records, or run the following command at a command prompt: netdiag /fix
13. The standard zones that were previously Active Directory-integrated can be converted back to Active Directory-integrated on the replacement DNS server if it is a domain controller.
14. Verify that the SOA resource records on each zone contains the correct name for the primary server and that the NS resource records for the zone(s) are correct.
inSSIDer is an free, award-winning Wi-Fi network scanner application for Windows Vista and Windows XP.
It scans networks within reach of your computer's Wi-Fi antenna, tracks signal strength over time, and determines their security settings (including whether or not they're password-protected).
NetStumbler, the most popular Wi-Fi network scanner, is free, but it hasn't been actively developed for years, and it doesn't work well with Vista or 64 bit OS.
inSSIDer, on the other hand, works like a charm on both Vista and XP, 32 and 64 bit, and it's open-source.
This must-have for hunting down Wi-Fi networks on the road.
Works with internal Wi-Fi radio
Wi-Fi network information (SSID, MAC, data rate, signal strength, security, etc)
Group by Mac Address, SSID, Channel, RSSI and "Time Last Seen."
Graph the strength of received signal in dBm over time
Filter access points in an easy to use format.
Highlight access points for areas with high Wi-Fi concentration.
Open source (Apache License, Version 2.0)
AHCI (Advanced Host Controller Interface) is present on newer Intel chipsets such as 975X (ICH7), P965 (ICH8), and P35 (ICH9). AHCI mode is enabled in the BIOS and 3 settings are commonly available: IDE, AHCI, and RAID. The last two (AHCI and RAID) require a driver floppy and the F6 method when installing Windows XP otherwise the hard disks won't be detected.
AHCI mode brings 3 main advantages:
Supports NCQ (Native Command Queuing) allowing SATA drives to accept more than one command at a time and dynamically reorder the commands for maximum efficiency.
Supports hot plugging of devices
Supports staggered spin ups of multiple hard drives at boot time
However, in the real world the performance difference isn't huge.
The problem is that if you installed Windows in IDE mode (i.e. you didn't use F6 and supply a driver disk), then simply changing the BIOS setting to AHCI mode and rebooting will cause Windows to fail and will require a repair install. Most people have been advising to reinstall Windows if you want AHCI enabled.
Here you will find the sollution :
Copy of the article is here (5.07 kb)