The biggest thing is that you can find and manage the printers if they are installed on a server. This and the drivers can be installed for all clients on the server.
Im having a issue with a backup script. It copy's our DB from one server to another at night. Its a simple xcopy batch. The odd part is that if we run it manually (click on the batch file) it takes about 5 mins to copy 3gb of data from a NT4 server to a win2k3 server. If I run it as a AT...
This is how I usually do it.
Install your printer on the SBS. Do this by adding a port, select tcp/ip port,use the printer ip. Install the printers drivers. Share the device, and tell it to list in the directory.
The printer should now show up for the xp clients while browsing the AD...
So both TS/RDP servers are on the same WAN? Going through the same router/firewall? If so you need to change the listening port on one of the TS servers to another port, and allow it through the firewall(both hardware, and software).
Im glad you solved your problem.
Printing was a big hurdle for us with TS. In the end we used print servers at our remote locations, and installed them as local ports on the TS.
The printer port mapping native to TS is really bad.
It sort of depends on how you use the domain/AD. If you do not take advantage of the OU, and roaming profiles. if you dont want/need the version of exchange that comes with SBS2k3, if you are not worried about the security stuff that you get running a domain, then why bother?
I personally...
BSOD is almost always a hardware or driver issue. Not enough computing power would manifest it self in slow performance.
I would back track the changes and upgrades made that relate to when the problems started. Also do a mem test and make sure those modules are still good. I have learned...
I found the work around
uninstall windows component Internet Explorer Enhaced Security Configuration
or set the address of server where mapped drive reside on Trusted Sites,
Adding the trusted site did nothing for me, Uninstalling that component worked. You will need to reboot after.
Yeah, I saw that , and tryed editing the script with no luck. The Reg hack works, however I then have to do that to all my clients, which makes me a sad panda : (
Im running exchange on my sbs 2k3 server. Every time a client logs onto my AD, it resets the default mail account to the exchange account. I do not want this behavior (you would think there would be a flag for this some place). Anyways, I found that this gets set from a file in...
Running outlook2k3 on a sbs 2k3 AD with Exchange 2k3. We use exchange as a secondary mail service, so I set the local Outlook clients to use oup pop internet mail as the default account. However after each reboot exchange is reset as teh default account. How can I over ride this?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.