Search results for query: *

We have deployed W2K SP4 to our environment and are now recieving the following error on the workstations: Application popup: Explorer.EXE - Application Error: The instruction at &quot;0x77f8c1bb&quot; referenced memory at &quot;0x<various>&quot;. The memory could not be &quot;read&quot...

We have a growing environment of Terminal Servers running mostly MetaframeXP. Is there good documentation on how to distribute sw to this farm using sms?

Try adding the following to your sms_def.mof file. Be sure to backup your original. class AddRemovePrograms { [key] string ProdID; [PropertyContext(&quot;DisplayName&quot;)] string DisplayName; [PropertyContext(&quot;Publisher&quot;)] string Publisher...

If you have your MOF set to collect add/remove program entries, you can just query for the patch. I find that this is sometimes misleading as files may not update until a reboot is initiated. The best bet is to go to the MS q article and identify the files the are changed for the particular OS...

We use sms to deploy patches using batch files and qchain. A select group of users prefer to run the advertisment non-mandatory. I set up the package to run non-mandatory and after they have run the advertisment and installed sucessfully, they have a record of the package in the completed...

A simple solution would be to run network discovery, (you state that users may connect connect to another domain, not network) Results will tell you if discovered devices are clients. You may want to make sure remote client installtion is not selected first.

In our single site, the site server has lost communication with one the bdc logon points. The error that appears in the site status is as follows: (replaced server name and domain name) SMS NT Logon Server Manager failed to find a suitable drive on domain controller &quot;servername&quot; for...

Are you referring to SMSCliToknAcct&? This is an account on non-domain controllers that SMS grants temp admin rights as needed to install SW, ect. It removes this account from local admin group when no longer needed. Cannot explain why clients are not showing up without more info. Are all...

We are in the process of moving our sms 2.0 SP4 on NT to W2K and SQL2000. We cannot modify logon scripts so our plan is to remove the site boundaries from the current site and let workstations uninstall the client sw. In the meantime we will build the w2k environment. When it appears that all...

Thanks for the feeback. I do plan on a phased approach by subnet. My subnets contain as few as 9 and as many as 250 clients. Do I need to break my larger ones down even farther? I plan on making advertisements available at night, even though we are a 24/7 operation. I will be deploying only...

Thanks Rod - I have read these already and they are very good. It does not speak to the site transfer settings wizard though. If I wanted to have the site remain in production thought this exercise, would the following procedures be adequate? 1) Install a new version of SMS on Windows 2000...

We will be moving our site from a NT4.0 to W2K with SP4. The database is moving from NT4, SQL7 to W2K and SQL2000. It appears from documentation that the best way to do this is using the site transfer settings tool. Is there a prefererred order of doing these activites? Any pre-reqs? OS or...

We are in the planning stages of deploying SP4 to about 1600 w2k workstations in a single site. Given a size of about 130MB for the package and a backbone of atm and gigabit ethernet along with 100MB nics, how many clients per Distribution Point per advertisement would be appropiate? To put it...

I suggest a simple batch file using the copy command

I have read MS reccomendations on how many DPs needed in a site. What I cannot find is what method a client uses to determine which DP it will get packages from. MS says it is a random process but I notice some DPs getting much more activity than others suggesting it is not based on some...

Discovery is independent of client installation. After running network discovery, use one of the client installation methods to install the client such as remote client installation

I know SMS creates a unique guid on each client workstation. Has MS developed a method to include the SMS client in an image to avoid the task of installing after imaging? I know our antivirus tool can perform this function. Thanks

Once you have completed network discovery and the SMS database has been populated, deleted any records you do not want the SMS client installed on and then enable windows remote nt installation. Clients will have to be in the correct domain be in a valid subnet and have an sms record to be...

Check out Q289877 - depending on what you want to do, you may have to slightly modify the query statement