Can I keep one machine from becoming a client?

[Rasslor]

I have a question about keeping just one particular machine from becoming a client? We have a machine that we use to create our baselines from and don't want any of the packages to be distributed to this one machine. But as soon as we put it on the network it begins to download everything. Can this be blocked my machine name, or MAC address? Any help would be appreciated.

Brendan
brendan_conway@hotmail.com

 

[BobS53]

What I have done it create a text file with no data (e.g. nosms.sms or noscript.flg). Then in your login script, check if file exits, if yes you can either exit your login script or goto a section that bypasses the check and install SMS section of the login script

 

[RodTrent]

And...if this client is NT/2K/XP and you are using the Remote Installation method, there's a couple things you can do to keep the client from installing.

Make a registry modification:

http://www.myitforum.com/articles/1/view.asp?id=138

Create a 0k MS file:

http://www.myitforum.com/articles/1/view.asp?id=201

Rod Trent
Microsoft.MVP.SMS
=======================================
Main site:

http://www.myITforum.com

=======================================

 

[puterdude01]

Brendan,
I read in a forum somewhere that if you create an ms folder under the winnt folder for nt for emample when the client tries to install it can not because the folder already exists. I have not tried this but it has stuck in the back of my mind. I would assume there would be errors generated about sms being unable to install on that client and not the cleanest way to work around a client install, but sounds like it would work.