awarberg1

Yes, the major hindrance is that sbs2k3 must the the only DC in a domain. Furthermore it wouldn't be possible to let another w2k3 machine be DC, as that would require exch2k3 to be installed on that machine - which is not possible without purchasing a (quite expensive) exchange server, as the one included in the sbs package will only install on a sbs2k3 DC. @Arkady As I wrote initially, backing up and restoring system state would include the entire registry, which is corrupted after the upgrade I made so this would gain me nothing. I'm aware that the sid's in the registry must be backed up and restored however. Any other ideas on how to crack this nut? Best regards Andreas

Hi guys, I administer a small sbs2k3-windows xp network. We have one sbs2k3 domain server with exchange 2k3 and one windows 2003 stan dard server, which is just a member of the domain (NOT member domain control ler, yet anyway). The SBS2k3 machine was initially sbs2000 but was upgraded a few months ago. Normally I don't upgrade OS's since certain things tend to corrupt as was th e case with our sbs2000 to 2k3 upgrade. At this moment, everything works reasonably well but I would like to have th e option to reinstall the domain controller in case something goes wrong. How can I do this? I know that reinstalling the server and then restoring a system state backup would not change anything as system state backups include the registry, whi ch is probably the most corrupted part of the OS after an upgrade, thus I wo uldn't gain anything. I cannot transfer the domain controller roles to our windows 2003 standard s erver, as a sbs2k3 installation must be the only domain controller in any ne twork, thus I would not be able to transfer the roles back, as I see it. Is there anything else I can do to do a clean reinstall of our dirty sbs2k3 installation? Of course I could recreate AD and group policies etc (since it is a small ne twork), but this could easily become a very time consuming - as well as high ly error prone - task for me to do. I hope you can help me. Best regards Andreas

Hi Ryan, This is great! I am able to define what is to be installed. Do you know if it is possible to configure the virus definition update interval through wininstall le 2003? Regards, Andreas

Hi guys, I'm administering a small Windows 2003 domain. We are using group policies to install software on our Windows XP clients. Although it would be possible to install via GPO directly by using the "Symantec AntiVirus.msi" file I would like to make some changes in what is installed. For instance, I dont think our users really need the SAVHelp component... The "Symantec AntiVirus.msi" file accepts commands from the command line to control what is installed, but as far as I know, it is not possible to issue commands to a GPO installed package. I have searched the Symantec knowledge base and found this article: Symantec article discussing MST transforms, which suggests creating a MST transform file (we already use a transform file for our Office installation) to make changes to the installation. So I have become acquainted with Orca, which generates MST files, however, I wouldn't know what to "transform" in the MSI file to make my desired changes appear. Symantec KB doesn't talk about configuring what is installed using MST files. Have you got any suggestions as to how I might make changes to the installation with GPO distribution in mind? Thank you. Best regards Andreas