canasia.org

As everyone has pointed out, running real graphics on a server isn't an ideal situation. And I'd agree that a better solution is to run it in a VM. However, all that being said, when dealing with ATI, I'd strongly suggest that you simply state that you're trying to update the drivers on your Server 2003 SP2 domain controller. Throwing in SBS to the mix will guarantee that they say it's not supported . When, in fact, it has nothing to do with SBS, and everything to do with installation on a Domain Controller, I strongly suspect. The best workaround for something like this is to get the drivers installed during the initial install, before SBS is fully installed and before the machine is an actual DC. Then leave them there. There should be no need to update the drivers later. The issue, of course, is that there is no such thing as a local administrator account on a domain controller. Or any local account. All accounts on a DC must be domain accounts.

Thank you all for replying. From the top, after my last reply... Susan: The DC is not going to shud down in two weeks, as it will be activated and will serve as DC for two more PC (home lab). The driver was downloaded from Internet and had no problem allowing that content. I need SBS on a live machine (for various reason). Maybe IT will host some VM, not the other way around. Russ: The card doesn't mention Server 2003 specifically (as 99% of cards don't mention that anyway). We both know that 2003 and XP have the exact same driver model. Yes I've used the card before in SBS, I already said so. Install didn't go well, because after choosing the first basic options, it didn't even go on, giving me a WINDOWS message (not a driver specific mesage) as I mention above. We also both know that the manufacturer of the card won't even EVER bother to reply (been there, done that with other hardware). Hands-on support software since it needs explanation (if this has smth to do with the thread, which I doubt), means it is one of the machines I use to troubleshoot others by seeing an ACTUAL machine with the ACTUAL OS. Why it is not a VM as many suggested? Because it is also used as my home server (as extreme as it may look), since... its there. It has a legit license so why not. I know very well that a server is not intended as a desktop system, but I am willing to overlook that, since I only have a finite number of machines at home (which is my company's lab extension - as happens with many). In fact a server system has served me (no pun intended) as a desktop for the last 4 years, doing a VERY good job with it. (though it was plain Server 2003, no SP, no R2, no SBS) Dave: I have a good driver. I've used the same download on other machines. The thing I have already tried (I think I mention it in my other post) is that indeed I tried installing the driver by updating the normal VGA driver. No it did not enable dual-head, in fact this is what killed even the clone display I had up to then. ATI is VERY commonly used in Servers (much more common than nVidia, although I cannot give statistics). It is up there with on-board intel and (old) S3 solutions. In I *am* surprised that Catalyst won't work. All the prerequisites are fulfilled and it just gives me some security error (that I *am* willing to ignore if it let me). Russ (again): No this server is not only used for business. It is not used as gaming machine either. If you read below, you will see that I (in some way) followed your advice on swapping the card. Yes I will be using SBS also as a workstation. Except the extra services it runs I don't see a reason why I shouldn't. We are not talking about a company domain, just my home lab. As I write above, done that with success for years (in fact the last server never game me even a bit of disturbance because it is a server ). I don't see how this parallels with a live grenade in my mouth. Will an ATI driver mess Exchange service? Will it mess domain schema. I very much doubt it. Charlie: I agree, mentioning SBS will mess things up on paper like in fact happened... in here. When it actually has nothing to do with the problem. The workaround you mention, is what I (accidentally) did in my first install. I should have followed... myself and do it again. Can't go back now. Indeed I know what it means to use a local account (let alone an administrator) on a DC. Not a problem in my case though as I've explained above. I am willing to take the (very low in my case) risks. Anyway thank you all for the replies. Issue was solved differently: I installed an nVidia card. nVidia drivers (FULL PACKAGE as available in their site) installed fine. In fact even the latest beta. Of course ATI hasn't replied to the ticket at all (and would be 100 times worse if I in fact contacted the actual card manufacturer). So consider this issue closed but not really .