anuragyadav

Thanks for the suggestion, not sure I can reduce the list to 50. I will post some updates in coming days if I succeed.

Sorry, I wasn't clear enough. I can for sure get the username before the deployment starts and also scan for user's membership of AD groups but how do we pass this information to make task sequence install the applications needed. We have 1000+ applications and same number of AD groups. I think we cannnot manually create all the application install steps in the task sequence. So, I wanted to know what are your thoughts on acheiveing this? I can create a script to query AD groups and pass on the list of group of which the user is member but have no idea how would I use that list. May be set Coalesceapp? Not sure how to do it though.

Hi, thanks for great article. In your task sequence all the applications have to be pre-created as tasks and then you check whether to install or not install a particular application upon membership of the computer in AD group which is associated with application. I have a requirement to install applications during OSD task sequence based upon membership of users into AD groups. We have the user to computer UDA preconfigured. We also have ConfigMgr user collections querying AD groups. But the challenge is to install application based upon user membership of a AD group. What do you suggest as best way of handling it? Many thanks!

Hi, Can you please explain it in more detail? I have a requirement to install applications during OSD task sequence based upon membership of users into AD groups. We have the user to computer UDA preconfigured. We also have ConfigMgr user collections querying AD groups. But the challenge is to install application based upon user membership of a AD group. Can this be done without scripting?

I have exactly the same issue. Pxe is messedup after upgrading to SP1. Were you able to resolve it?

Not earlier but I just read the post. I agree there are many ways of setting up OSDComputerName. I am in process of deciding what method to use. i.e use a script to set OSDComputerName and run in the task sequence or use the method told posted by deploymentguys on technet. I have 2 questions basically - 1. I want to setup the computername according to Location and asset tag. For example.. SWE9898989 where swe is location and 9898989 as asset tag. I used MDT Locations and hardcoded gateway and location information. The gateway was not picked up probably because connection from WinPE to the MDT database was not made. However, the name changed from XXX12132 to MINNT-* format. I am not sure why. 2. What is the best way of renaming the computername. I will be using offline deployment quite a bit in my project and may be the connection to MDT database will be a problem. Thanks!

Hi, I am new to this. I have mdt+database which I have integrated with sccm2012. I created a MDT task sequence (client installation sequence). In my MDT workbench I have used database to set location settings dependig upon gateway. Basically following this post - http://blogs.technet.com/b/deploymentguys/archive/2011/08/05/dynamic-computer-naming-in-zti-deployments-using-mdt-and-configmgr.aspx However, for some reason i can't get it working. The computer name is always picked up as default like MINNT-xyz123 . When I saw the bdd logs I do see a section where the OSDComputerName was set to the desired value but it changed to default format again. I am uploading the logs for your reference. Appreciate your help in this. BDD.log CustomSettings.ini smsts.log smsts-20121226-044320.log ZTIGather.log ZTISCCM.log