Jump to content


Established Members
  • Posts

  • Joined

  • Last visited

About JacobE

  • Birthday 07/19/1988

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    London, UK
  • Interests
    Photography, Scuba Diving, Hi-Fi, Technology, Zombie Apocalypses.

JacobE's Achievements


Newbie (1/14)



  1. Hi guys, Where I'm currently working the 2012R2 environment is hardly used, they use it for security patching and OS deployment, thats it. Anyway, it was setup by a previous monkey and the content Library was left to go on the local server C drive, which is only 250gb, and its now full up. So they want to move it and have offered me a network drive. Now, I know I can use the content library transfer kit to move it no problem, but the question is access...is SCCM going to be able to access it from a networked location, or does it have to stay locally?
  2. Oh really? Dammit. I was hoping to have a cleaner setup than that. Powershell isn't an option due to our security, VBS is fine though (yes, I know)
  3. Hi guys, OK. So I've created an app-v4 app with 4 icons, with a deployment type assigned to each icon, giving me 4 deployment types. Obviously when deploying though, you deploy the whole package and by default with no additional settings, it'll deploy all 4 icons to the user. I want to add a dependancy/requirement to make it that it detects AD Group membership, confirms if the user is a member of it and then if so, deploys that deployment type. Is this doable? It'll be deployed to a specific user collection (which runs its own AD Group query to pull that AD group into that collection) so it won't be doing AD queries across the whole of our AD.
  4. Hi all, Cast your mind back to 2007 and the virtual application deployments within it...it had this handy toolbox called "Remove this virtual application when it is no longer advertised" Where the fudge has this gone in 2012? It was perfect for us, and now without it it's causing us a whole host of issues, especially when it comes to licensing with our Virtual Apps. Mainly what is happening is user A will login to a meeting room PC to host a meeting or one at our DR site for a DR test and the app ofcourse gets downloaded to their machine they're using. So now they have 3 copies of it and as far as the license true up is concerned, is using 3 licenses of it. We could obviously setup device affinity, but the problem is then in the case of a DR situation nobody would have their apps follow them to whatever random desktop machines the user ends up sitting at. So what we need is the virtual application to remove itself off of machines when the users access is removed (say if they leave for example) and if they haven't logged into the machine for X amount of days. Can anyone think of a way of doing this? I've been doing some research and found this http://blogs.technet.com/b/gladiatormsft/archive/2013/05/22/app-v-and-cm-2012-grrrrrrrr-where-did-remove-this-virtual-application-when-it-is-no-longer-advertised-go.aspx- which explains about an uninstall query which is fine but it will only run once per user, so if a user accesses a meeting room machine half a dozen times in a year it will only run once. Here is a technet link my colleague created - https://social.technet.microsoft.com/Forums/en-US/1a8ee1a1-f8d7-4d1c-b322-701a95524220/removing-appv-applications-when-the-usermachine-is-no-longer-a-member-of-part-of-an-ad-group?forum=configmanagerapps- this helps explain our issue further. TIA Jake
  5. Hi all, For a while now I've been trying to figure out and get my head around a better understanding of 'Unknown' Clients within SCCM along with trying to eliminate them. We have adjusted our clean up rules for older machines which has reduced this down a lot, but I would like to figure out why we keep getting odd ones here and there. This will help with our monthly stats. For example, on our Baseline configuration we are currently seeing this: So I'm assuming 'Client check passed/Inactive' means these are machines which were previously responding to SCCM but are currently switched off, unplugged, offline etc. IE basically defunct old machines or currently not in use and will be removed from SCCM within 30 days. What I don't understand is the 'Client check passed/Active' column. The machines are online, pinging, the SCCM client appears to be functioning correctly from what I can see yet we are still seeing these 24 machines. Can anyone offer an explanation to why this could happening, or suggestions on where to check to work on resolving this please? I'm going to guess that ideally we would have X amount of machines as inactive and won't be older than 30 days and then 0 as 'active' in the unknown tab. Thanks in advance! Jake EDIT: To add to this, just looking at another deployment on the same collection and now seeing this result. This is something that baffles me even more, why are these unknown clients not consistent even though it's looking at the same collection?
  6. Hi all, Now I've done Offline TS builds before at previous companies and never had an issue...which is why this is becoming a head scratcher, an annoying one at that. So I've built a USB stick with the unattended option ticked. The machine applies the OS from the stick and then it goes to install the first application. This is when it has problems. It fails pretty much instantly and the error log looks like this. It's a weird one to say the least! The error code from googling just says it needed to do a controlled reboot, which I'm assuming is because it fails...but it doesn't say why it failed! ARGH And breathe...any ideas folks? TIA Jake
  7. Hi there, Thanks for the reply, I looked into this more and found out the machine in question had a USB stick plugged in, a 16gb one and it tried writing to that (which would not be possible as we don't allow USB sticks to be written to. Why it defaulted to E, I'm not sure still. C had over 200gb free on it.
  8. So I sent out a TS last night to update 5 applications and all were successful bar one machine...heres the log file. Its such a weird one, it's saying it cannot write to the volume e: yet the applications shouldn't even be writing to E: and should all be writing to C:\ Anyone seen this before? Ta
  9. Well I'm going to set in stone this is for core applications only so I avoid just that. Core applications get updated a couple of times a year, if that. So it won't be much to maintain
  10. Mini thread revival and update! So going back to this, I looked into customizing reports but my SQL skills just aren't up to scratch! So after looking into this a bit more I'm exploring the configuration baseline possibility. Initial tests look good and its pretty easy to setup, specifying against registry values/product codes I can then create a subscription to a report "Summary compliance of a configuration baseline for a collection" to run once a week and store it on a server somewhere, and from that create a scheduled task to email out said report out to myself and the team. Therefore we would know which machines are not compliant. The key is making sure remediation is switched off so it doesn't enforce any changes for we would like to control that ourselves, and it keeps my manager happy...it'll also be pretty easy to maintain as core applications are not updated all that often. Thought I'd add this in for anyone else looking for a similar solution. TLDR - Use the configuration baseline for what it was designed for.
  11. I've since found out that the above is for MSI apps only, not Virtual Apps. Anyone have any ideas?
  12. Hi Marc, Yep when setting the to 'Available' ensure you select the notification to the Config Manager Client and then the users will get a bubble stating new software is available and they'll get the option to install.
  13. Hi all, Ok so we migrated all of our virtual applications in as 'applications' into 2012R2 when we came from 2007 R3. I need to change the source file paths on all the virtual apps so we can decom the server they currently sit on. I've looked on how to do this but it apparently isn't straight forward. I found this link here: http://blogs.technet.com/b/configmgrdogs/archive/2013/02/18/moving-your-package-source-after-migration.aspx - which unfortunately has not worked, when I try to the powershell command it does not error, but it doesn't change the source path either. Can anyone help? Thanks! Jake
  14. How did you create the appv packages? Was it via the ODT? if so did you specify visio specifically?
  • Create New...