Jump to content


pvr02

Established Members
  • Posts

    62
  • Joined

  • Last visited

Everything posted by pvr02

  1. I can confirm the client successfully sends the HW inventory to the MP in the clients logs. However, on the MP side, I don't get anything in my MP_hinv.log. It hasn't seen any activity for over 24 hours.
  2. Background: Recently we were attempting to get Asset Intelligence working. We had some issues with the online connector. When troubleshooting this we came across some patches that fixed a certificate issue KB2483225 and then later KB2733615. After installing these patches (and rebooting) and waiting to attempt another asset synchronization I was informed that hardware inventories were no longer working. I checked the MP_Hinv.log file and had not received anything as of the time the patch was installed. This is a major problem for us as software is not being deployed to new builds. I have scrapped working on Asset Intelligence until we can resolve the hardware inventory issue. Currently: 24 hours into troubleshooting this, It appears that everything is working properly with the exception of Hardware inventories. There has not been anything new in the log file. The clients have been testing and are performing the hardware inventory and are successfully sending it to the server (however it never seems to make it there) I have attempted to uninstall BITs, Reboot, Reinstall BITs (this did result in about 10 minutes of hardware inventories coming in before stopping). I have uninstalled both of the above patches that were installed and Restarted - No results I have uninstalled and reinstalled BITs again, without getting any additional results. Everything in the Component Status and Site System Status are OK, I have rebooted numerous times without success. The only errors I am seeing are related to IIS. EventID 5189, Source WAS, The description for Event ID 5189 From source Microsoft-Windows-WAS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. The following information was included with the event: CCM Server Framework Pool 7 This is SCCM 2007 Running on Server 2008 R2 SP1. Any ideas? Thanks in advance.
  3. We recently pushed out a piece of software we need on everyones computer as soon as possible to our main location. The package installed nicely on most computers. However, we noticed that quite a few were in the state "Waiting for content". After checking into it we noticed that the laptops that were out of the office on VPN (which we have considered a slow link) was not getting them. After checking the advertisement we confirmed it was set to "Do not run program" within a slow or unreliable network boundary. We changed it to "Download content from distribution point and run locally" yesterday. However today, the clients are still waiting for content. My guess is that the client still thinks that it should not run the program. Is there anyway to have the client re-evaluate the advertisement to learn it can now download it? Thanks in adance
  4. We deployed a package and had the download settings as "Do not install software updates" over a slow network. The client knows there is something to download and just says "Downloading" but never receives anything. This is how I believe it should work as it was connected over our VPN segment that is marked as slow. Then we change that package setting to "Download software updates from distribution point and install". the client continues to say "Downloading" and doesn't download anything. Now I have noticed that if we let it sit for about 2 days or so, the client will eventually download it. I'm assuming this has to do with the client still thinking it shouldn't download it. Is there any way to manually update the client so it knows it is ok to download the package? Thanks in advance.
  5. In our case we have our VPN subnet marked as being a slow boundary. We have a user who works outside of the office on VPN most of the time requesting software. The software packages are all set to "Do Not Run Program" over a slow boundary. We also do not publish software to the users. In this case, the user is not getting the software we are advertising to them. Is there anyway to override this setting either on the client side or on the server without changing the advertisement to "Download content from distribution point and run locally" for everyone? Thanks in advance
  6. Collections -All Windows 7 Systems -All Windows 7 SP1 Systems We are in the process of setting up our SCCM 2007 server and have roughly 50 or 60 machines on the system. Unfortunatly, we are in a development/production stage. Before I start making some changes, I wanted to be clear on a few items. If we have an advertisement assigned to the collection "All Windows 7 SP1 Systems" and change the advertisement to the collection "All Windows 7 Systems" will the package re-run on on all of the Windows 7 SP1 Systems? Also If we have an advertisement that is assigning a package to "All Windows 7 SP1 Systems" and create another advertisement with the same package that is assigned to "All Windows 7 Systems" will it re-run the package on the Windows 7 SP1 Systems? Thanks in advance
  7. Or, is there anyway to add more specific items in the "This profram can run only on specified client platforms:"? I wouldn't need to separate them, if i would specify only Windows 7 Pro instead of All x86 Windows 7.
  8. Currently we have been pushing out full copies of Windows 7 Professional to all of our workstations. However we are looking into pushing Windows Thin PC (based off of windows 7) for alot of our old warehouse machines. We currently have the machines being split up into sites. This collection is where we assign our software. This WQL query is: select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.SMSInstalledSites = "XX1" and SMS_R_System.Client is not null We are new to the SCCM game and are not familiar with all of the coding yet, but what we would like to do is add a OS check into this as well. Basically on the query above set it to check for the installed site "XX1" and that the client is installed. Also check to see if it is Windows 7 Pro. We then want to create a second collection with the same type of query but checking for Windows 7 thin pc. Any ideas would be extremely helpful. Thanks in advance.
  9. Does anyone know any way to disable the ability to do the wallpaper slide show? We are planning on using BGInfo to display information on each users desktop wallpaper but when it rotates to another image that info is lost. I've already tried to force 1 wallpaper for all, but that wasn't approved. They want users to be able to change the wallpaper.
  10. We are in the process of getting our first SCCM server in place and running. We have our typical software packages created and ready to go. However, I am wondering how everyone manages software that requires unique keys. Specifically something like Adobe Acrobat Pro, PhotoShop, SnagIT, etc... We only have a few copies of this software and each one has it's own individual keys. Thanks in advance
  11. I haven't tested this yet in SCCM but creating a test bat file using the variable %1 you mentioned and calling it in windows seems like it will work. Greatly appreciate the help.
  12. We are currently setting up a SCCM 2007 server (no MDT at this time). I have the Collection Variable "OSDComputerName" set so it prompts us for the computer name. Besides that, I have have a Batch file that I would like to run during the OSD Take Sequence but it requires some user input for a field "Username". It is possible for me to create a Variable called "OSDUserName" and have that information passed along to the batch file? Thanks in advance
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.