Search results for query: *

Thanks for the info, the server is a w2k DC in the same domain as all of the secondary sites, which incedentally are also on DC's ( only servers on site ).

My concern is whether moving the site to a Non-DC will foul up any of the SMS Accounts, all the default accounts have been used SMSService etc.

I haven't played around with SW Metering yet so I don't know if this will work but I'd check the machines that don't report the extension an see if Explorer is configured to Hide known extensions. ( I have come across a similar problem, not in SMS, when explorer wasn't configured to display the...

The SMS Primary Site Server and Site Database currently reside on the same Windows 2000 Advanced Server which is configured as a DC. I am going to move the SMS Primary site to a new server and I would like the new server to just be a member server. Does anyone know if this is...

Chris, Thanks for the SW-Metering tip, I have to implement that soon. I sent a request for Clustering Support in Topaz to the SMS Wish List, hey it's worth a try.

Thanks Chris, everything I have found on the net suggests the same. Any idea if Topaz is going to sort this?

I know that an SMS Site Server can not be part of a cluster as the SMS Services are not designed to switch over on failure, but I was hoping that the databse could reside on a SQL Server that is clusted. Much to my dismay Microsoft says no, but the article (Q237366) only mentions NT4 Clustering...

After deploying an assigned package Advertisement Status reports more program successes than programs started. When I view all program success messages some resources ( in this case machines ) report 2 successes about 15 minutes apart? The package was set to SMS restarts machine does this...

As the first stage of moving my Primary Site to a new server I need to move the SMS Database to a remote SQL Server. Is this a straight forward database move or are there any issues with SMS configuration as well.

I have had had to do a few MSI Setups using SMS and I also used the technique above, however I did create an admin installation point first ( /a switch ) this makes the installation fully MSI resiliant.

When an assigned package is cancelled by the user and Advertisement Status registers a program error will the SMS Client re run the package itself? If so how long before this happens.

When you say you have created the collection from the query on the test domain are you using the actual query from the test domain or have you created the same query in the prodution domain and used that? Does the query limit the results to a specific site code?

Have you tried installing the SMS Client manually on these machines? To do this connect to \\sever_name\SMSLOGON\x86.bin\00000409 ( SP2 ) and run smsman.exe. Don't specify a site server let the client find one itself ( site boundries ) once it has installed wait for a bit and the components...

Try editing the value for Server under: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\AdminUI\Connection

No, it is a different issue. It causes out of memory errors and a process called winoldapp crashes the system when the RC Agent installs. Upgrading to SP3 doesn't resolve the issue according to what I have read.

On Windows 98 the RC Agent can cause the machine to hang when it installs ( Q266232 ), once the RC Agent is installed would removing it cause similar problems?

Having recently rollout out the SMS Client to our desktops I came across the Remote Control Agent installation bug on Windows 98. In all the documentation that I have read there has been no mention of whether I'll get the same problem if I disable the RC Agent and it uninstalls from the Windows...

Don't quote me on this one but when you configure your discovery methods make sure you don't check the box which says Modify users logon script ( this put's the command to execute smsboot1.exe in the logon script and everyone who logs on in the site will install the client ) then only users with...

I seen this problem before when working with remote control and Windows 2000 and NT clients. Without SMS 2.0 SP3 you will have problems controlling an NT mchine with a W2K machine and vise versa, NT to NT and W2K to W2K doesn't seem to be a problem.

In the near future I am going to be required to move my existing sms primary site to a new server which will have a different netbios name. I am sure this is going be a rather difficult task and mean a lot of work reconnecting the 70+ secondary sites that have just been created. Any help would...