My goal since I began looking at ConfigMgr and planning my upgrade for OSD functionality has been to move completely off MDT 2008 and do everything within ConfigMgr. There are a couple of areas with my current setup that I haven't been able to get to work natively within ConfigMgr so I'm fishing to see if anyone else has tried to accomplish these things and made them work: 1. Chassis specific actions in a task sequence. With SMS 2003 and MDT it's been as simple as the IsLaptop and IsDesktop default values that get gathered based upon the WMI ChassisType to determine if the machine is a desktop or a laptop. I've not been able to do that in a ConfigMgr task sequence. Since it appears I am limited to WMIC queries which cannot handle ChassisType then I'm forced to add a query for every hardware model that is a laptop or a desktop, rather inconvenient. 2. SQL database connections. I really wish MS had added a TS action to query a SQL database. One strong point of my current setup is that with CustomSettings.ini I can specify certain subnets that are to query a SQL database where they get variables populated to drive the deployment. It seems there are some things I need to do that require me to continue to use CustomSettings.ini or write my own complex code to perform in ConfigMgr. 3. out of the box variables that you would think ConfigMgr would be using and would be readily visible do not seem to be there. All those OSDxxxxxx variables in SMS 2003 have to have been replaced with something. It seems very different in ConfigMgr. I've gotten some list of built-in variables, but they're not all available all the time. It depends on where you are in the deployment cycle. 4. Logs. Does ConfigMgr have the equivalent of SLShare from SMS 2003 with MDT? It's been very useful with my current setup to have each phase of the deployments dump a log to a common network share. Now that all seems to be replaced by reports built into the ConfigMgr console. That stinks! Thanks for any replies on these. |