Joining to a Domain Controller

[jkp*74]

I am currently engaging a vendor to setup a Domain Controller. I intend to join this Fortress server to the Domain Controller.
1) Is there going to be any impact to the current installation of Fortress?
2) Any setting need to be made?
3) Any risk?
4) If i don't join this server to the Domain Controller while the client PC is joining, will the client still able to access Fortress?

version: 1.1.4.18402
Server OS: Win Srv 2003 for SBE, SP2

[lbauer]

Is the Fortress Server currently on a workgroup?

Will the name of the Fortress machine change?

Is SQL Server on the same machine or a different machine than the Fortress Server?

[jkp*74]

1. It only says - Domain: secondary.micromodular.com when i look at My Computer->Property->Computer Name
2. It joining to a Domain Controller (DC) does not require a change in its name, then the answer is No. I need to check with the vendor. As of now, the Full Computer Name is secondary.micromodular.com
3. On the same machine

[lbauer]

You may need to uninstall and reinstall Fortress after joining the domain. It's possible that certain permissions, URL's, IP addresses and pathnames will change. If these are written in the database or in the registry, then they would no longer be valid unless you reinstall. All your Fortress information is in the sgmaster, sgvault and sgdragnet databases, so if you do need to reinstall, backup your databases, uninstall Fortress, leaving the databases when prompted, then reinstall. The installer will detect the existing databases and use them.

[jkp*74]

Ok, the server has been joined to the Domain Controller. Connecting locally from the server is OK but the client is having problem connecting remotely to it.

For Vault Client, this is the error message:
"Unable to connect to http://www.mmsvault.com/VaultService. No server was found at the specified URL. Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client. Web Exception: Unable to connect to the remote server"

For Web, this is the error message:
"The connection has timed out
The server at www.mmsvault.com is taking too long to respond."

Can't find a command to attach file, so i will printout the log here:
# SourceGear Vault Server
----3/22/2010 12:48:36 PM sgvaultsystem--()--
System Started
Version 1.1.4.18402
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = C:\WINDOWS\Temp\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 4320
SGVault Working Directory = C:\WINDOWS\Temp
SGVault Server URL = http://www.mmsvault.com/VaultService
Identity = NT AUTHORITY\NETWORK SERVICE
----3/22/2010 12:49:38 PM joel--www.mmsvault.com(127.0.0.1)--SSL Disabled Login
----3/22/2010 12:54:13 PM sgvaultsystem--()--
System Started
Version 1.1.4.18402
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = C:\WINDOWS\Temp\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 4320
SGVault Working Directory = C:\WINDOWS\Temp
SGVault Server URL = http://www.mmsvault.com/VaultService
Identity = NT AUTHORITY\NETWORK SERVICE
----3/22/2010 12:54:24 PM admin--www.mmsvault.com(127.0.0.1)--SSL Disabled Login
----3/22/2010 12:54:30 PM admin--www.mmsvault.com(127.0.0.1)--SSL Disabled Logout
----3/22/2010 1:12:23 PM sgvaultsystem--()--
System Started
Version 1.1.4.18402
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = C:\WINDOWS\Temp\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 4320
SGVault Working Directory = C:\WINDOWS\Temp
SGVault Server URL = http://www.mmsvault.com/VaultService
Identity = NT AUTHORITY\NETWORK SERVICE
----3/22/2010 3:36:50 PM sgvaultsystem--()--
System Started
Version 1.1.4.18402
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = C:\WINDOWS\Temp\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 4320
SGVault Working Directory = C:\WINDOWS\Temp
SGVault Server URL = http://www.mmsvault.com/VaultService
Identity = NT AUTHORITY\NETWORK SERVICE
----3/22/2010 3:36:56 PM admin--www.mmsvault.com(127.0.0.1)--SSL Disabled Login
----3/22/2010 3:36:59 PM sgvaultsystem--()--
System Started
Version 1.1.4.18402
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = C:\WINDOWS\Temp\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 4320
SGVault Working Directory = C:\WINDOWS\Temp
SGVault Server URL = http://www.mmsvault.com/VaultService
Identity = NT AUTHORITY\NETWORK SERVICE
----3/22/2010 3:37:09 PM admin--www.mmsvault.com(127.0.0.1)--SSL Disabled Login
----3/22/2010 3:41:27 PM admin--www.mmsvault.com(127.0.0.1)--SSL Disabled Logout

I have performed the re-installation of Fortress & iisreset. I must be missing something here.

[jkp*74]

It turns out that Windows Server 2003 SBS cannot join to a domain controller. I only realize this when the server keeps shutting down every 30 min or 60 min. It will take a while for me to revert back the system.

[lbauer]

Sorry it didn't work out. Let me know if you have additional questions.