In the MMC go to Site Database\ Site Hierarchy\ #SITENAME#\ Site Settings\ Connection Accounts
You can set the Client and Site Systems accounts there. The Site System account will only be needed if you Netware in the environment. The Client account must have the correct permissions to access...
Keith no easy answer here. We have run through many tests in our lab and have NEVER been able to rename a server without a full reinstall of SQL and SMS.
We have also had little success simply moving a server from DomainA to DomainB.
Hopefully you have a good backup handy.
Mike
We have been able to fix this problem simply by either uninstalling and reinstalling the client or by reinstalling the default mouse, keyboard, and video drivers.
Hope this helps.
Mike
I ran your query successfully by adding an inner join. Since I don't know exactly what you're querying for, you will have to change appropriate values.
Hope this helps.
Mike
select distinct SMS_R_System.ResourceId
from SMS_R_System
inner join SMS_G_System_VIDEO
on...
Should be able to script a package based on the uninstall option of the Novell client.
Problem is the Novell uninstall usually does not restore the correct network settings after uninstall.
Not a lot of help. Good Luck
Mike
Are the machines still in a Site? If they are not the client will uninstall by default after 60 days.
If they are still clients you can send an uninstall package that will run silently and in the background, which requires no user interaction. Note that the client will not be fully uninstalled...
True Elbert, WBEM is installed with SMS but we still had client connectivity issues when we upgraded to SP2 and we determined that WBEM was not being updated.
We now run a check during logon scripts for certain DLLs to verify and/or update the correct version of WBEM.
Also the version of WBEM...
One thing you will need to watch out for - your backup may go ok with no errors but will fail on restore.
I have had this happen to me on more than one occasion. Test your backup first with a full restore to make sure your data is not corrupted.
Also you didn't mention if you had any WIN95...
Our laptops do not run SMS over dial-up connections we check for the dial-up IP subnets during the logon script. If a dial-up subnet is detected the script drops out.
As to logon from different locations, if you check the SMS applet in control panel on the client, you can check the radio box...
I agree, make sure your Logon points are there and you have the proper IP subnets configured.
Do you have the Network Logon Client Installation enabled?
Or NT Remote Client install?
Have you checked your connection accounts and do they have the proper permissions?
Just some things to check...
We have had problems with SP6 and 6a, Microsoft reccomends only installing these SPs to address specific problems. We are currently running SP5 and have no plans for SP6.
Next step 2K!!
You need to remove the PNP call from the registry, I believe it is located in HKEY_Local_Machine\Software\Microsoft\RunServices.
We had the same problem with our Win95 clients, the Aztec software that installs the PNP piece takes a 'snapshot' of the AUTOEXEC.BAT and attempts to recreate it if...
You need to remove the PNP call from the registry, I believe it is located in HKEY_Local_Machine\Software\Microsoft\RunServices.
We had the same problem with our Win95 clients, the Aztec software that installs the PNP piece takes a 'snapshot' of the AUTOEXEC.BAT and attempts to recreate it if...
(copied from Windows NT magazine)
A good way to keep a close eye on the Registry is to use SYSDIFF in Microsoft Windows NT Resource Kit. With SYSDIFF you can make an image of the Registry before you install new products, then compare that image to the working Registry after you install the...
Win9x clients cannot 'see' the network when not logged on. It is not possible to install aplications using SMS to Win9x clients unless they are 'on' the network.
Mike
Heenick on the server side -
SMS_Executive - many other services are under this one SMS_Site_Backup - manual service for site backups
SMS_Sql_Monitor - connection to the SQL database
SQLServerAgent - self-explanitory
On the Client Side -
SMS Client, SMS Hardware Inventory Agent, SMS Remote...
Patricia this is the qeury we use...
select distinct sys.Name, sys.LastLogonUserName, sys.OperatingSystemNameandVersion, sys.ResourceId, sys.ResourceType, swfile.FileName, swfile.FileSize from SMS_G_System_SoftwareFile as swfile inner join SMS_R_System as sys on sys.ResourceId =...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.