-
You could also create a policy on the existing OU and filter it so that just one user gets that policy applied.
-
DirectX 10 comes with Vista, and Vista only. But... that's for games basically. The Aero interface is actually DirectX 9 based. DirectX 10 won't be a requirement for Vista Premium untill 2008
-
Okay, first of all: always configure a pagefile, period. And second... I ALWAYS set the pagefile fixed. I've done this before back on Windows NT 4. And ever since on 2000, XP, 2003, ... On servers this is actually a big improvement and a big issue. Especially on multi-user servers like Terminal Servers/Citrix and other "heavy load" programs. Just consider this simple logic: suppose you let Windows manage the size of the pagefile. If and when Windows needs to expand the size of the pagefile a slow process will start and performance will take a big hit. Is that what you want to be happening? I don't. And what's more: the article that's referred to is back from 2004... and in the IT business that's ages ago... I'm a big fan of Mark & co, but from my own experienc I'd say: set the page file fix
-
Forestprep and domainprep are mandatory, Exchange setup just doesn't start if it does not detect them. I guess this is a AD security issue
-
Try the good old elimination technique: disable AV on the gateway and test disable AV on PC and test and so on..
-
I didn't mean to say that the licensing service isn't a good and handy tool but technically, to make things work, it isn't necessary
-
From a technical point of view, you don't really "need" a license server. In fact, you can easily disable the Licensing service. Beware, this is not the case on an Small Business Server. The Terminal Server Licensing service you need if you're deploying a Citrix/Terminal Server to distribute TS CAL's
-
Just a guess: are you connected through RDP, or is anybody at that time? I'd suggest finding the source DSN that's causing the problem
-
Try the most recent one you can find I'd say
-
There are 2 things: - Share permissions - NTFS permissions Share permissions are by default set to "Everyone - Read only" on Windows 2003. This means that, even if the NTFS file permissions are ok, users still have only Read rights.
-
You did everything OK on your client PC/outlook But... On the Exchange Server box, it has also has to be configured. By default in Exchange 2003, Out-of-office replies don't go outside the organization (aka the Internet). The administrator has to configure this.
-
What is the problem exactly? There's also a LegacyExchangeDN attribute, that's is among others used by the ADC for example
-
When a user is added to a group, he/she is required to logoff and back on. This is why: a SSID is gererated at logon, and group membership is one of the components that generate the ID.
-
A tricky one: Go to Control Panel, User Accounts Click on the advanced tab, and then you'll find a button "Manage Passwords" Then check wether the server you want to connect to is listed. If it is, just remove it because it is not needed there
-
I use PopCon. Very easy to use, very fast! And cheap too! Great site with a lot of tips and tricks (not only for Exchange) http://www.petri.co.il/index.htm