Jump to content


pxedave

Established Members
  • Posts

    63
  • Joined

  • Last visited

Everything posted by pxedave

  1. I just noticed there is a "always install client" tick box when pushing the SCCM 2012 client from the console. I can't remember if I tried this. Maybe ticking this will uninstall the old SMS client for me(?) I'll try it and report back...
  2. NOTE: Since creating this post I've learned that you can define .CMD and .EXE installations as Applications (as well as MSI and App-V) by choosing the Manual option on the first screen of the Application creation wizzard. I don't see any reason why anyone would define anything new as a Package anymore; I see Packages as being a legacy thing for those importing data from an existing SCCM 2007 setup. Starter for ten: Like Applications, Packages can be deployed as Available or Required. Like Applications, packages deployed as Required show up in the Software Centre. With Applications, as well as specifying which OS it CAN installed on (i.e. whitelist) you can also specifiy which OS it CAN NOT install on (i.e. blacklist). With Packages you can only specify which OS it CAN install on. UDA and OS deployment does not work with Packages; Packages being deployed (Required) to User Collections do not get installed until after the user logs on for the first time whereas Applications get installed ahead of the user logging on.
  3. ... A bit more on this. I'm also having to set a requirement in each of my apps to only install on Windows 7, otherwise SCCM will try and reinstall apps when I distribute the client to my XP machines prior to my Windows 7 OS deployment. It's all good fun.
  4. Fair enough. We plan on having one user collection per app (to perform the install) (for all apps, app-v and msi) leaving users in the collections as required. Assuming we don't get this feature back I don't fancy having to setup equivolent uninstall collections/deployments for every app just to manage tidy-up. Maybe setting this up just for our apps that have tight licensing constraints or monitoring the number of installs and occasionally setting up uninstall jobs might be a good compromise. I guess this leads on to uninstalling with UDA: I see that I can deploy an app to a user and it will install on their primary device without them being signed on. I would hope uninstalls would work in the same way. And if I rebuilt their primary device, I wonder if it would try and run all uninstalls targetted to the primary user even though the app isn't installed. I bet it would...
  5. Right, I think I've got a handle on this. At this point I think our Windows 7 deployment including UDA will look something like this: 1) Define all apps (reworked for Windows 7, optionally setting primary device = True) 2) Define Windows 7 deployment Task Sequence (adding in a few standard apps not in the image) 3) Create user collections for all remaining apps (likely one per app in our case) 4) Create deployments for each app to collections (likely all Required rather than Available) 5) Add user accounts to the appropriate collections 6) Define one primary user for each device 7) Roll out the SCCM client to our existing devices (XP in our case) 8) Create a device collection to target (night-by-night, probably 500 or so at a time) 9) Deploy the Windows 7 Task Sequence to the device collection. As I said, I can't think of any easy way to prevent apps from being inappropriatly deployed between steps 7 and 8 above other than to set a requirement within each app excluding XP. The downside is it's an extra step when defining all my apps, but hey ho. All constructive cryticisim welcome.
  6. Ooh that's not what I wanted to hear. So it's not just me then. I'm now wondering if the developers have removed the "Remove this package from clients when it is no longer advertised" setting from 2012 because they no longer want to provide this feature (or because they had problems implementing it in the first place)...
  7. Really? That would be nice. Maybe there is something wrong with my lab. I'm hoping to move to RC2 next week. Has anyone else seen this appv-gets-removed-when-user-is-removed working (or not)?
  8. ... If it's the same issue as we had I'm pretty sure un-ticking the PXE option on the distribution point, restarting the WDS service and re-ticking the option fixes it for us...
  9. ... But as I said above, if the collection excludes XP devices then the deployment of Windows 7 isn't going to install the app for me... because the machine isn't in the app collection because the device will still show as XP in the console until after WIndows 7 is installed, the SCCM client has been reinstalled and the collection has had time to update(?)...
  10. This may seem like a daft question but I want to prevent my XP clients from installing software before I've had a chance to deploy WIndows 7 to them and I'm not sure the best way of doing it. I'm thinking that when I setup UDA for all my machines and add my users to the correct application deployment groups ahead of deploying the OS so that the apps get installed at build-time I'm guessing the SCCM client will try and reinstall all my apps early. I was thinking I would target my XP clients with modified SCCM client settings which turn off software deployment but this is sure to prevent me from deploying the OS to them too. Then I thought I would just limit all my application collections to Windows 7 or above rather than "all devices" but this would mean the machines wouldn't be allowed in the collections until after they are Windows 7 and therefore no apps would install at build time. I'm thinking the best way might be to build a requirement into each app so they won't install on XP, but it's far from the set-in-one-place-and-forget-about-it solution I was hoping for. Any better ideas?...
  11. Folks, anyone got any thoughts on the best way of automating the uninstall of the SMS client and the install of SCCM 2012? I'm going to have to face this one at some point. I had hoped that deploying the new client would remove the old one but the deployment fails (with an upgrade version error); you have to uninstall the SMS client in advance. I'm thinking that deploying an SMS program that creates a local scheduled task to perform the job might be the neatest. Wouldn't it have been nice if MS had of added some /uninstallall switch or something rather than assume an upgrade...
  12. Is your WDS service started? This sometimes needed a restart (in RC1 anyway). Also, your machine you want to build is listed in SCCM and you've created a deployment for it?...
  13. OK Peter, thanks for confirming. Does anyone know how this should work? Is it the case that the App-V app should become unavailable to a user when they are removed from the SCCM deployment collection? Now this setting doesn't exist maybe this behaviour is now default? (In which case I have a problem with my lab). I can understand why this setting was there as it sounds like something most people would want to do...
  14. Looks like it's not just me: http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/48ab8e86-c157-40ec-94e9-192fa073bd07/
  15. Folks, I'm playing with App-V app deployment solely using SCCM 2012 targetted by user rather than device. Deployment works fine but when I then remove a user from the group I was expecting the app to stop working and/or disapear for that user at some point. I've seen a "Remove this package from clients when it is no longer advertised" banded about (SCCM 2007?) but I can't find such a setting anywhere. Is it me?
  16. OK, applications being deployed via a device collection (rather than user collection) also install before the final reboot / ctrl+alt+del when rebuilding a machine which is great. I hope to only target via user collections (changing the deployment type to primary-device-only for apps that are licensed per machine rather than per user) but it's good to know we have app-deployment-at-OS-deployment-via-device-collections as a fallback as well as UDA. Now I just need to 1) get all my products defined as Applications ensuring to set a primary-machine-only deployment type where applicable 2) create one collection per app 3) create one deployment per app targetting the appropriate collection 4) populate the groups with the appropriate users 5) ensure all users have the correct device as their primary. No pressure!
  17. OK it looks like this works right out of the box. I tested this by 1) creating a user collection for the app, 2) deploying the app to this user collection (required not available), 3) putting a user account in the user collection and 4) making this user the primary user of the machine I rebuilt. I then rebuilt another 3 times using variations of users and machines and it seems to work every time; the app being installed before the first ctrl+alt+delete. Next test, what happens at OS deployment time when you target device collections rather than user collections in advance, but I'm guessing it will work in the same way. We're very impressed with the RC so far...
  18. ... Why don't I set a user against one of my machines, deploy an application (required) to that user, do a build and see what happens. Watch this space...
  19. Hi. You're describing hard-coding the userid to be used by the build within variable (collection or device). Am I right? If so, we would need to create one collection per machine or modify device records individually(!?) I'm just wanting the build to use the userid that has previously been set against my machines (using "import user affinity"). I feel like I'm missing something here...
  20. Hi anyweb. So you're saying I do need to make some changes to my TS to make this work? I'm guessing I need to set a variable just to turn on this feature forcing the task to get the user(s) from SCCM database? Any other clues? I'm a bit lost here, sorry...
  21. ...Also, assuming UDA is all about creating a user collection per app and deploying apps to these required (rather than available), I forsee that some of our apps will need to target device collections instead of user collections (due to strict licensing requirements). Can/will an OSD task sequence also automatically install apps targeting the machine as well as the user of that machine? Forgive me if I'm missing something here...
  22. Hi, Zero touch deployments (SCCM 2012 RC Windows 7) all good. Now I want my task sequence to also install some applications based on the UDA that has already been defined in the console. I see a number of guides on modifying the task sequence to PROMPT the builder for UDA (variables etc) and make use of this but does anyone know how I set things up for this to work for zero touch? Do I have to add variables to the TS to make this work or does this just work out of the box?...
  23. You're not the only one. See post below where I asked the same question. Both networked and standalone DVD worked fine for me (SCCM 2012 RC) http://www.windows-noob.com/forums/index.php?/topic/4629-non-pxe-methods-of-building-bare-metal-win7-machines-using-sccm-2012/page__fromsearch__1
×
×
  • 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.