baker999

I've created user collections that lookup AD group membership. I now want to deploy software to the machines those users log into and install the software for the machine. Understandably this isn't a 'clean' way of managing the software deployments because users could log into multiple machines - but the software we're deploying is free/unlicensed so sprawl is irrelevant. We're SCCM 1603 and I can see the deployment running, but it fails. Presumably because of the context the installer is running. If I install it against a device collection, it works. Presumably because the install is run in the SYSTEM context, and not user. How can I get around this? Is it possible to configure service accounts with admin rights to runas for a user deployment? Or is there a cleaner way? Cheers!

It seems the .cab file has to be installed under PE mode, not during a logged in session. Never mind. I have another question - I have tried to tailor your example to substitute RegionValue for OSDComputName variable (which is declared in PE environment before the OS is deployed) . So, if OSDComputerName like TOK , then Japanese language settings are applied etc. I have read that SCCM can't handle 'like' or 'contains' queries (and for reference, I used a Custom Variable, same as you do) to declare OSDComputerName. I'm now finding that the components aren't installing, but no idea where to check on client logs where this went wrong, and why. We want to build PC's by the region, and SCCM to detect the OSDComputerName, then apply the relevant language packs and UI languages depending on this variable. Do you know which logs to check, or anything to watch out for when doing things this way? I think the reason my deployment failed has something to do with OSDComputerName not being a custom variable, but I'm not sure how i should declare this in the: IF OSDComputerName like TOK THEN SET OSDLanguage to ja-jp Declarations... attached example

This was massively helpful thankyou! I will try to implement your full solution shortly, however, I want to be able to install ja-jp language pack as an isolated task sequence (deploying the LP to a desktop that is already imaged). I have created a new task sequence, used the Install Language Packs Offline option and added/distributed the contents (.cab file containing the language pack) - there is only 1 step in the task sequence (to install the LP) - and it seems to fail shortly after downloading the content. error code 0x00000032. I doubt the 'full' solution will work if the standalone install of the LP using sccm's wizard-task sequence will work. Any ideas why this task sequence fails? Or how we can retrospectively add a language pack to a pre-built machine (whilst the user is logged in/off)?