Recent content by AJP69

I was not aware the SBS2k3 had removed TS, are you sure it that you have actually installed it? If so then MS has made a big mistake because small companies will give their users access via the admin accounts which is a security risk. TS sessions are very thin, I used two VPN's (one Cisco and...

Useful to know but no DCHP on our DC

You probably also discovered that under the wndows scheduler you can specify and account and whether the user needs to be logged in.

For such a small network It is hardly worth it, you could install DHCP on the second server but not authorise it in AD but this would require you to manually authorise it in event of a failure. You can splice and dice DHCP in so many ways, some people like to do it by subnet or segment, others...

For such a small network I would not bother messing aroudn with the roles, just implement a good backup strategy. DNS and DHCP are totally seperate services and you can duplicate those as required, well you can for DNS. For DHCP you have to be configure seperate pools of addresses to avoid...

The problem is that XP was developed 2 years after 2000 and workstation drivers have become huge ugly things that not only print but fix bad breath and a host of other things you don't need. Just check the system tray of the workstation and the CPU usage in task manager, some manage to...

You are so right! I think before that tool was created TS admins used to hide in closets at the mere mention of printing!

If only life were so simple. Some of those roles are show stoppers so make sure you backup the AD regularly. As always, it depends: Are those DC's doing anything else? How many users are there? Is everyone on one site? Some roles are best kept together on the same box. Updates are...

How quickly we forget! One reason that many people will not upgrade from W2k Terminal services is that in W2k3 MS charges per user/device. Under W2k any W2k PC or XP PC workstation includes a CAL (Client Access License). So if you keep it all Windows Server 2000 you will not incur costs...

I have a fairly strict policy when it comes to printers, this is sometimes difficult as I do not have control of the client workstation IT. First off I say no to printers that do not have a processor (i,e, those that use windows). I also say no to printers that are connected via serial port...

Thanks for that link, I will check it out, luckily we got rid of WINS and Netbios when we moved to Win2000.

STOP right there. You need to be careful about installing any old printer driver on a terminal server. If you do chances are you will create a whole host of problems for yourself. Bad drivers can cause the spooler to break, this stops printing dead, then when you put it back on printouts go...

Of course it might be easier to just go look at the domain controller and run the appropriate Active Directory. Assuming you have some other reason, you can run a batch file that outputs the data >> to a text file. the NBTSTAT command pointed at an IP address will tell you the machine name and...

I have a similar situation, you need a combination of tools. First the workstations, if you can stick in a thin client, the sort you get from Wyse. Then you have the system launch a terminal server session automatically on boot. The TS session can be set to launch a specific app based on the...

Thanks for the reply. Sorry I should have said it is Aactive Directory integrated with secure updates turned on. The DNS server is for the database and terminal servers only, it does not receive or forward from other servers. In theory the updates could only come from the virtual database...