Jump to content


Jaybone

Established Members
  • Content Count

    88
  • Joined

  • Last visited

  • Days Won

    3

Jaybone last won the day on August 5 2016

Jaybone had the most liked content!

Community Reputation

4 Neutral

About Jaybone

  • Rank
    Advanced Member
  1. Update: ~20 hours later, that job has transferred a whopping 20MB. 0_o
  2. Hi, all. Came upon something I've not seen before. Trying to push the Config Manager client to a new server, it was going excruciatingly slow. Reading up on it led me to look at BITS stuff. Settings were all good - non-existant, actually. The only thing that helped was to change the job's priority from Normal to Foreground. That got the transfer done more or less instantly. So now the client's installed, but there are new BITS jobs stacking up. I can't get any Windows Update info from it to the CM server, etc. Now, this server sees a sustained 250-275mbit/s of inbound netw
  3. Update of a sort: Yesterday - ran ccmsetup /uninstall and watched uninstall log and event log for completion Rebooted when it finished removed ccmsetup folder and remnants of ccm folder Verified with WBEMtest that root\sms no longer existed. Pushed install from server stepped back to give things some soak time Today - same old nonsense CmRcService insta-disables itself and logs that we've disabled it SendSchedule.exe /L only returns six things sending it an Evaluate Machine Policy schedule says it's successful, but nothing c
  4. Hi, all. Scratching my head here, and hoping someone has some insight on this. Sometime between last Thursday and yesterday, Remote Control stopped working on at least one device in a remote office. The service instantly disables if it's manually changed back to Automatic (delayed). It does fall within a boundary used for site assignment. Remote Control settings are set at both the default policy level and in a policy applied to a device collection this thing is in, both set to allow. CmRcService.log claims that The ConfigMgr administrator has disabled the Remote Control fe
  5. Running 1610, I stumbled across something yesterday, and I'm wondering if anyone else has seen this: changing just the name of a query used to populate a collection breaks the collection. Steps to replicate: Change the name of the query being used as a membership rule for a collection. Collection's icon gets an hourglass, even though nothing about its membership actually changed. Hourglass doesn't go away, and collection membership no longer updates. The first time I saw this was with a query-based collection looking for %server% in operatingSystemNameAndVersion. Ev
  6. For Office 2013, MS themselves still recommend 32-bit unless the 64-bit functionality is specifically needed. Or has that changed? As far as the OS... some of us are still stuck running 16-bit legacy garbage that can't be run on a 64-bit OS, with no time or budget to get it converted to something more modern. If one has the time to implement virtualization to get around that, great, but not everyone does.
  7. I could find approximately nothing with Google, other than the standard documentation, which is either wrong, or I'm completely misunderstanding. From its own help: SYNOPSIS Gets Configuration Manager alerts. Example 1: Get all alerts PS C:\> Get-CMAlert Except it doesn't. It misses a ton of them. On our new 1606 site, it returns only 17 of 28 alerts, and none of the ones I'm actually interested in (SCEP alerts). In another forest with 2012 R2 + CU3, it returns 186 of 192. Better, but still not all. Are certain things, e.g. SCEP alerts, not considered "Conf
  8. Anyone seen this? It only appears to be affecting Office 2010. Updates, generally older ones, that meet the criteria for installation - Office 2010, not superseded, Security or Definition Update categories. They're not getting installed. A report run against a computer that shows as needing them comes back with some updates only marked Required, while others are marked Required and have a deadline, but none of them show as being approved. How can an unapproved update get deadlined, and if it meets the criteria, why isn't it approved? Blowing up all Office 2010 update groups and cre
  9. Alternatively, you could have three collections: 1 = AppNameCollection 2= ExeVerCollection 3= ComboCollection - instead of query, just include AppNameCollection and ExeVerCollection I forget the details of why, but I've had to do this for Java, to get both 32-bit and 64-bit instances into one big collection - trying to write a single query that would catch both would just not work as I expected. My expectations were probably wrong, heh.
  10. Try unchecking unknown computer support, restarting WDS service, re-checking unknown support, restart WDS service again, and see if it starts working?
  11. Sorry, but this really deserves a... http://lmgtfy.com/?q=80220014+sccm
  12. After changing up my search terms, came across this same type of question on Technet, answered by Garth and others. https://social.technet.microsoft.com/Forums/en-US/0f096508-2440-456e-ae78-72f4e4271a89/installed-applications-version-is-less-than-sort-order?forum=configmanagerapps Apparently it's a string comparison, not numeric, so yes, the leftmost digit being 9 vs 1 explains it.
  13. How big are these apps, and how big are the client caches? I don't remember the details, but we saw something similar when deploying the Dynamics AX client. The default cache size is, I want to say, 5GB. The AX install was 7+GB. Clients would try to install it and fail since the app was too big to fit in the cache. Solution was to increase the cache size on the clients. I'm not familiar with the specific Autodesk stuff you're using, but in my experience with Autodesk Infrastructure Design Suite, I know their installers can run to the tens of GB, so you might be running into this sa
  14. We've always had collections set up so that we could tell quickly which clients had installs of Java below a certain patch level. Our criteria for this was to look for: Installed Applications.Display Name is like "%java 8%" and Installed Applications.Version is less than "8.0.XYZ" for 32 bit installs, and a corresponding collection for the 64 bit ones, where XYZ corresponded to the current version. Java 8 Update 91 was 8.0.910. With the new version that came out the other week, Java 8 update 101, that version number is 8.0.1010. I'm wondering if that switch from 3 digits to 4 digits i
×
×
  • Create New...