Recent content by Karactur

Does anybody have any info on whether or not Microsoft will release an exam to Certify SMS2003? Karactur.

SMS Site Component Manager detected that site system "\\SMSECONDARY" is currently in use by SMS site XXX. I have recently installed a secondary site, although all "seems" well, I continually receive this error on an hourly basis. The best I can tell, is that I have the site registered twice in...

I am curious as to the possiblity that an Advanced client, if placed in a foreign SMS environment, would "Roam" to that site? What prevents the client from connecting to another SMS server and site?

Does anybody know if clispy.exe has any command line switches? I want to set it up as a utility within SMS2003 but would need to be able to set it up as a command line switch to point to the system I want. clispy.exe is from the SMS 2003 Toolkit 2 utils.

Try this report, and let me know how you like it. select CAS.AdvertisementID,ADI.AdvertisementName,CAS.LastAcceptanceStateName,CAS.LastAcceptanceStatusTime,CAS.LastStatusMessageIDName,CAS.ResourceID from v_ClientAdvertisementStatus CAS Left join dbo.v_AdvertisementInfo ADI on...

THIS IS IT!! I was able to successfully find enough documentation and suggestions to get this to finally work. I modified the SMS_DEF.MOF with the following. It will enumerate all versions of McAfee on your clients. All advanced clients MUST compile this locally for it to work. It can be done...

C'Mon Gurus!!! Lets try to help out the crowd!.. This is of those things most admins need in SMS2003. We have to follow our clients and their dat versions clearly. Has anyone succeeded here?

Microsoft has released a scan agent for this issue. It works like a charm. http://www.microsoft.com/downloads/details.aspx?FamilyID=C4745685-9521-4B63-A338-0B3E2DCBF2BB&displaylang=en

I have found resolution to this issue. When Software updates creates a package, the admin defines the location to store the package, and I assumed this was to be the final shared location, BUT OOOOOOO NOOOOOOO, it STILL created another sms shared package, not in the regular location on the DP...

Lets Update: I have found that Advertisements ARE working, HOWEVER, its the Software Updates that do not. When I try to deploy a Critical Update, the system fails, and reports back "Bad Environment". All the logs point to "Path not Found" If I run the command manually at the client...

I need a resolution to a puzzle I am having. I have recently upgraded to SMS2K3-SP1, and have found that all new advertisements to LEGACY clients are failing, stating "Network" problems. It seems the Legacy clients no longer see the DP. This is only a factor with packages POST Sp1. Anything that...

Sorry dude, I'm pretty sure Metering only watches for process open/close. Which means only specific .exe applications.

You can always setup a direct membership or query rule within the collection. Create a collection called "IPs" select properties and membership rules. Create a query that enumerates all Ip's in your environment, or all IP's similar to your list. Then simply "Check" all the systems you want in...

A shot in the dark, but have you setup your site address to the secondary site on the primary site server. Without it, it would not update. Just a thought.

Did you upgrade recently? Are you now using SMS2k3? If it is 2k3 you could verify the smsreporting.log file or the SMSReportingInstall.LOG file for clues as to why it failing. I would suggest using SMSTrace to view the log.