Q
Quizzed again
I appologize for he poor title of this post.
My IT group cloned my 3 servers. SQL, App, Web.
Because the servers are clones they were using the production config
database, etc. I disconnected the cloned servers from the production servers
by running the WSS admin Wizard and selecting disconnect. I then created new
Config Database on the cloned SQL server. and all looks good in the cloned
system.
Now when I go to the production servers, the WSS Central Admin site shows
only my SQL box as existing.
I am not sure if I should use the WSS Config Wiz to reconnect the farm?
If I use the WSS Configuration Wizard to establish connection to the
existing farm, it sees the config database but it wants to use a new port.
Should I let it use a new port? It recognized that the port I was using
exists and is being used.
Also should I stop the Sharepoint Central Admin web site in IIS Manager
since the wizard wants to make a new one with a new port?
My IT group cloned my 3 servers. SQL, App, Web.
Because the servers are clones they were using the production config
database, etc. I disconnected the cloned servers from the production servers
by running the WSS admin Wizard and selecting disconnect. I then created new
Config Database on the cloned SQL server. and all looks good in the cloned
system.
Now when I go to the production servers, the WSS Central Admin site shows
only my SQL box as existing.
I am not sure if I should use the WSS Config Wiz to reconnect the farm?
If I use the WSS Configuration Wizard to establish connection to the
existing farm, it sees the config database but it wants to use a new port.
Should I let it use a new port? It recognized that the port I was using
exists and is being used.
Also should I stop the Sharepoint Central Admin web site in IIS Manager
since the wizard wants to make a new one with a new port?