Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Removing site system automatically assigned a role by SMS

Removing site system automatically assigned a role by SMS

Removing site system automatically assigned a role by SMS

Im having difficulty removing a BDC which was automatically picked up and assigned the role of a CAP by SMS.

Reason i need to do this is because i now need the server to be a secondary site server.

But during installation it keeps telling me this server is a member of a site and all i can do to it is install administrator console.

Normal right-click on the site system, doesnt give me the 'delete' option.

Any ideas guys?

Thanks in advance

RE: Removing site system automatically assigned a role by SMS

You need to go into the Site Settings folder and then Site Systems folder.  Here you will see what systems are performing what functions.  Right click the server in question and select properties.  Deselect all server functions you don't want it performing.

John Rolstead

RE: Removing site system automatically assigned a role by SMS

Thanks Rolstead,

I had done all that. They are no longer CAPs or distribution points or anything else.. the only thing i see is that these servers are domain controllers.  The ones that are not domain controllers, i am able to right click and delete, but with the domain controllers - the delete option is not available.

I know that SMS goes out and grabs all the DC and makes them site systems, how can you stop that happening?  Even ones that are outside the boundary definition are picked up as long as they are domain controllers....   ?!??!

Thanks anyway Rolstead.

RE: Removing site system automatically assigned a role by SMS

You are right in that Lola.  All DC's in the domain that is added to SMS 2.0 will be installed as logon points.  Their is a Server discovery process that is not adjustable.  I am facing this issue right now with a phased deployment.  I will use the Master domain controllers as Secondary servers in each physical location.  But if I enable Windows Network Logon Installation and specify the Master domain, then all DC's will become logon servers.  I will see what effect this will have on their ability to still function as SMS 1.2 logon servers.


RE: Removing site system automatically assigned a role by SMS

I'm having the same problem now.  We just removed a BDC from our domain (gave it to another division of our company).  It's only function was as a logon point.  I've looked through TechNet and all the articles say that you cannot remove a site system automatically assigned by SMS (2.0).  I'm hoping someone has found a way to remove one.  Seems odd that you can't remove something when it's no longer being used.

Tom Thaden

RE: Removing site system automatically assigned a role by SMS

I have completed some testing in the lab.  I was able to install Secondary Site onto a machine that was a DC in Master Domain "GlobalCopy".  Primary Site server is a member server in master domain.  Added master domain to Windows Logon Installation.  All DC's were aquired through server discovery and made clients, smslogon servers.

SMS 1.2 SP3 and SMS 2.0 SP2 Beta

Apr 20 Process: Testing if SMS 1.2 Package/Logon Servers can coexist on same hardware with SMS 2.0 Logon point in Master Domain.

1. Installing NTPDCLAB1 as Package/Logon.
a. Added NTPDCLAB1 to list of SMS 1.2 Logon and Package servers.
b. Edit smsls.ini to point globalcopy domain workgroup to NTPDCLAB1.
c. Run script to confirm that clients can install SMS 1.2 components before SMS 2.0 Windows Network Installation is enabled on domain Globalcopy.
d. Added the Globalcopy master domain to the Windows Networking Client Installation configuration in SMS 2.0 Administrator console.
e. Enable “Modify User Logon scripts” to see what effect this has.  This will NOT be done in production.
a. SMSLOGON share added to shares on all Domain Controllers.
b. All other shares are unaffected.  SMS_SHR, SMS_SHRC, SMS_PKGC still valid.
c. The following files were added to Export\Scripts:
d. Script continues to run on clients with no errors due to SMS 1.2 smsls.bat file being stored in a subdirectory called “SMS” in the Netlogon share.
e. Tested remote control to SMS 1.2 clients.  No issues.
f.  Tested software delivery via Package Command Manager.

Apr 20 Process: Testing of Installation of Secondary Site to Master Domain DC with all SMS 1.2 components removed.
a. Remove SMS 1.2 client components via script on specified Workgroup.bat files.
1.  Copy file SMSREM12.bat to Netlogon\Updates and rename file to workgroup to be deinstalled.
2. Have users logon as normal.
3. Confirm that components are removed by checking for sms.ini file.
a. The MS directory remains after removal of client.  First job to new SMS 2.0 clients is to remove MS directory wherever it may exist.
4. Client removal process can begin, with installation of SMS 2.0 client software not occurring until Secondary Site is created and Site Boundary is assigned.  The script will try to install the software but will exit due to client not being assigned to a Site.  This is by design.
b. Remove all SMS 1.2 components from NTBDCLAB2, setting the SetupPhase value in SMS.INI to Deinstall.
a. NTPDCLAB1 remains active as GLOBALCOPY  master domain Logon/Package Server.
b. Removed SMS 1.2 Logon and package components from NTBDCLAB2 via SMS Admin console.
c. Wait for the SMS_SHR, SMS_SHRx share to go away.
d. Remove SMS_PKGE share and directory.
e. Remove client components from NTBDCLAB2 by setting the SetupPhase value in SMS.INI to “deinstall” and rebooting.
f. Verify that all SMS 1.2 component services have been removed.
g. All SMS client software must be removed from Master domain DC’s prior to adding the domain to SMS 2.0 Windows Network Logon Installation.  This is due to all DC’s being discovered and made SMS 2.0 clients.
c. Install Secondary Site to server
a. Requires domain, install drive.
b. Use the Global1\SMSSITECONN account.
c. Add the account to the Site Settings>Connection Accounts>Site System folder.
d. Have SMS install setup a new address to Secondary Site.  Standard Sender Type.
e. Set account to GLOBAL1\SMSSITECONN account for connections.
f. Have SMS Install setup a new address to the Primary Site. Standard Sender Type.
g. Set account to GLOBAL1\SMSSITECONN account for connections.
h. Run Install.  Wait approximately 30 minutes and exit/relaunch SMS Admistrator console.
i. After install is complete, select secondary site properties and turn on Software Metering Server service.  Put SWMTR directory on largest drive.
j. Components installed are:
a. Software Metering.
b. Client Access Point.
c. Component Server.
d. Distribution Point.
e. Site Server.
f. Enable all Client agents.
k. Enable Windows Network Client Installation.
l. Site Boundaries will be set to subnet that the Secondary server is on.  Add any necessary subnets.
m. Leaving Discovery methods set to default.  Primary Site will do this function.  Heartbeat discovery is on by default.
n. Create Collection for Secondary Site.  Name it according to physical location.

RE: Removing site system automatically assigned a role by SMS


I am facing the same situation with a mixed environment of SMS 1.2 and 2.0.  I have already installed all of my logon points.  Should I be expeciting a lot of problems. The DC's which are SMS 2.0 logon points are also SMS 1.2 Site servers.  Will this create problems??

RE: Removing site system automatically assigned a role by SMS


Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close