ICTCity

Ok, now I have time :P At cmd type: net stop w32time Modify this key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlags, under Value data, type 5, and then click OK. Then: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer\Enable NTPServer type 1 under Value data, and then click OK. Then cmd: net start w32time Now, on client / server side (NOT THE MASTER!) do the following: right click on your clock, change: At the top there are 3 tabs, select INTERNET TIME, then CHANGE SETTINGS and finally type the IP or name on the dropdown list. Done.

Hi, Now I've no time to write all the commands, but check this to configure one server: http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/7dc5e8f4-824a-432c-a2da-ac0e3fdf76fd/ (there are commands with w32tm) Then, on the client side, there's a policy which tells where to point.

Hi, Usually Windows Server 2008 should be installed on a server (HP, Dell, IBM, ...) to ensure the maximum compatibility. Anyway, you can use a "normal" workstation, USUALLY if it supports Windows 7 it can also support Server 2008. Regarding perfomance, there's nothing more to say... it's like a normale computer but running windows server. You should be more specific on what should this compuer do.

I'm happy that you resolved your issue... but... NetBios is required ONLY for netbios names, not for FQDN. According to this KB http://support.microsoft.com/kb/204279/en-us it can be permanently disabled. There are apps which still use netbios, but actually I think let netbios active is not a great (security) idea...

Hi, It makes sense! When you ping something: my.domain.local, the clients looks at resolution of my.domain.local. Which is ok. When you join a domain, the queries are more than one. Anyway, try the following (on client side): route /F ipconfig /flushdns Add the following line to the C:\Windows\System32\drivers\etc\HOST file: IP_DC domain.local IP_DC DC.domain.local Let me know.

Yes, you can: netsh int tcp set heuristics disabled I think that you should disable auto-tuning too.

Scale factor is a "trick" which should speed up network comunication. In fact it allows the windows size to be larger. Now, if I can remember right... by default it is enabled on Vista, 7, 2k8, 2k8 R2. Also, it shouldn't drop any connection if it fails... PROBLEM.doc

You're welcome!

Maybe on the server side, IPSec is running and all the related services cannot be disabled... Regarding print and tasks: From what I can remember no, they must be started in order to work. If you stop Print Spooler you can't even see your printers!

Hi, Check that ALL the drivers are up to date (verify with manufactures' website). Can you start the resource monitor and see WHAT hangs your server? Which process...

IKE and AuthIP IPsec Keying Modules > Set to manual. Distributed Link Tracking Client > mmmm you could disable this service, it maintains links up to date. If you move one file on another location over your network, it will update the path. Link-Layer Topology Discovery Mapper > Disable IPsec Policy Agent manuel started > Set to manual Base Filtering Engine > DO NOT DISABLE Internet Connection Sharing (ICS) > Disable Windows Firewall > Disable

Hi, I can't understand: That means you contact your server via internet from your client and you don't receive any answer? Which kind of protocol are you using?

Hi, Here's the solution: http://www.win2008workstation.com/ Probably you don't need everything, but all the answers are there :)

Install all the servers as usually do it. Run dcpromo on new server and join to the current domain. Install as DNS, GC, once everything has been replicated, change the DNS settings to your clients and finally run DCPROMO on the OLD domain controller in order to remove them from AD / DNS and so on. After that you will have only new DC running Srv 2k8. Quite the same story for FS. Use ROBOCOPY to copy folders from A to B (where A is old and B is new). Nothing more to do with permissions and so on. I hope this help. Cheers

Hi there :) Enjoy your stay!

The only "possibile" answer could be: the DNS haven't propagated all the rights for DHCP...

Hi and welcome! Enjoy your stay!

Why you don't create ALIASES on your DNS?

I hope not...http://technet.microsoft.com/en-us/library/active-directory-maximum-limits-scalability%28WS.10%29.aspx#BKMK_ObjectsThere's a limitation, but it's about 1 billion or something like that...

Hi, my suggestion is: 2 pc: install XenServer (free version) so you can have up to 5 VMs running on it (more tests) use a switch to connect everything together.

it looks like you have too much traffic. RDP into your server, stop WDS service and check if the problem persists. Let us know the result.

You have to use only "Windows" or your can user 3rd part programs?

it's up to you... you can schedule a job which starts at user's logon and open the connection via RDP.

Hi, You are currently doing the job that I'm looking for!!! Welcome :)

Wait... no hyper-v required. With RDP enabled, people will RDP to your server and they will use THE RESOURCES OF THAT SERVER! Hyper-v is to CREATE another computer... not RDP.