Jump to content
Forum²

F2 Staff

Forum² Admin
  • Posts

    843
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by F2 Staff

  1. The drivers that the OS installed work fine for me. Have you tried them?
  2. Could be your ISP throttling the connection or if you have a router you might have qos set too high for each connection.
  3. I use sub domains. I use one for the DC and one forthe Exchange server. I've never heard of that problem. How are users with laptops connecting from home? We use VPN to connect to the company lan and I always use the same laptop from work and home with same login. You can leave the printers setup as you have them.
  4. I use a software program called deltacopy. It's like xcopy with a gui. It should do just what you want.
  5. You'll probably have to open the ports. Windows Firewall on 2008 is real picky about exceptions. I had to allow the connection to the program and also open up the ports used.
  6. Have you set the correct username and password for the user the task runs under and dores that user have permissions to run the task?
  7. Are you installing in a dual boot environment?
  8. From what I've read the problem you're having happens when installing on a box with an Asus motherboard. The only fix I have seen was to change from sata mode to ide. Since that didn't work maybe resetting cmos and then configuring bios before install.
  9. Must be a driver problem. Does you motherboard need drivers loaded to install?
  10. Standard with 5 CALs will do it. If you only want to run wesites, no domain controller, then get the cheapest version.
  11. You should enable terminal services.
  12. Try switching you sata mode to ide. That should cure the problem.
  13. Make sure terminal services is installed and running and make sure rdp is enabled.
  14. Use computer manager to shut off secure passwords.
  15. You buy the domain. You setup Windows 2008 DNS and create a zone for the domain you purchased. You assign an IP to the domain in DNS. Create a directory for the domain files. Open IIS manager and add the domain to the server. If you don't buy a domain Windows 2008 will not create it.
  16. You have to buy the domain and then add it to the server using IIS manager.
  17. The link at Guy's blog seems to work now.
  18. 1: yes 2: yes This link will give some incite on how to join NT machines to a Windows 2008 domain. When a Windows NT 4.0-based computer tries to use the NETLOGON service to establish a security channel to a Windows Server 2008-based domain controller, the operation may fail
  19. TSZ Admin submitted a new resource: [plain]4 methods to add Server Core RODCs to your environment[/plain] - [plain]4 methods to add Server Core RODCs to your environment[/plain] Read more about this resource...
  20. Try turning off secure passwords.
  21. TSZ Admin submitted a new resource: [plain]Installing Hyper-V on Windows Server 2008, Server Core[/plain] - [plain]Installing Hyper-V on Windows Server 2008, Server Core[/plain] Read more about this resource...
  22. TSZ Admin submitted a new resource: [plain]Steps to install OpsMgr 2007 DB and Reporting on Windows Server 2008[/plain] - [plain]Steps to install OpsMgr 2007 DB and Reporting on Windows Server 2008[/plain] Read more about this resource...
  23. Set one up as DC. You can set up VPN that way users can connect remotely and have access to all the resources on the domain.
  24. You're right. I went to technet myself searching for the issue. I'll keep looking for an answer in case this scenario comes up to bite me. So far my clients want clean upgrades to 2008.
  25. It does sound like a cal issue. Did you use per device cals or per user cals?
×
×
  • Create New...