Peter van der Woude

It is correct that OSDComputerName is empty when it is not used. The name is actually stored in the read-only variable _SMSTSMachineName and that value will be overwritten with the value of OSDComputerName (when used). See also: http://technet.microsoft.com/en-us/library/bb632442.aspx

A trusted forest works almost the same as the local domain. Quote from http://technet.microsoft.com/en-us/library/gg712320.aspx You must have a forest trust to support any Configuration Manager sites that are located in other Active Directory forests. When you install a Configuration Manager site in a trusted forest, Configuration Manager does not require any additional configuration steps. However, make sure that any intervening firewalls and network devices do not block the network packets that Configuration Manager requires, that name resolution is working between the forests, and that you use an account that has sufficient permissions to install the site.

Yeah, that's possible. Small catch, you have to create it yourself via some script, or HTA and add that as the first step of the task sequence.

SMSMP=<FQDN of the server> See also: http://technet.microsoft.com/en-us/library/gg699356.aspx

As long as you use a Prepare ConfigMgr Client for Capture step during the capture task sequence everything will work as designed. That step will strip the client again.

Thanks for the kind words! I wrote down your wishes and they might show up in a future release

============================================================================================================================== To reach an even wider audience. This is a new tool, which I released this monday. >> Available via download here on the TechNet Galleries! << ============================================================================================================================== The script creates a form to show the Collection Details for a specific device. Normally, from within the console, it is hard to see what collection settings are all affecting the device. By running this script it will directly show the collection memberships of the device including the applicable deployments, maintenance windows, power settings and collections variables.It uses the ResourceId as input, so it can easily be used as a right-click action (see my own blog for an example). To use this script the following input variables are required: ResourceId - Specify the ResourceId of the device. SiteCode - Specify the site code of the ConfigMgr site. SiteServer - Specifify the site server name. Example: PowerShell.exe -ExecutionPolicy ByPass .\ShowCollectionDetails_v0_9p.ps1 -ResourceId 16777224 -SiteCode PTP -SiteServer PTSRVR02 Version 0.9 shows the following details: (New!) Tab – General; The Name of the Collections. (New!) Tab – General; The Id of the Collections. (New!) Tab – General; The Limiting Collection of the Collections. (New!) Tab – General; The Last Update of the Collections. (New!) Tab – General; The Last Membership Change of the Collections. Tab – Deployments; The Name of the Collections. Tab – Deployments; The Name of the targeted Deployments. Tab – Deployments; The Type of the targeted Deployments. Tab – Deployments; The State of the targeted Deployments. Tab – Variables; The Name of the Collections. Tab – Variables; The Name of the Collection Variable. Tab – Variables; The Value of the Collection Variable. (Updated!) Tab – Variables; The Type of the Collection Variable. Tab – Maintenance Windows; The Name of the Collections. Tab – Maintenance Windows; The Name of the Maintenance Window. Tab – Maintenance Windows; The Start Time of the Maintenance Window. Tab – Maintenance Windows; The Duration of the Maintenance Window. Tab – Maintenance Windows; The Recurrence of the Maintenance Window. Tab – Maintenance Windows; The Schedule of the Maintenance Window. Tab – Maintenance Windows; The Type of the Maintenance Window. Tab – Maintenance Windows; Whether the Maintenance Window is enabled or not. Tab – Power Management; The Name of the Collections. Tab – Power Management; The Name of the Non-Peak Power Plan. Tab – Power Management; The Name of the Peak Power Plan. Tab – Power Management; The Start Time of the Peak Power Plan. Tab – Power Management; The End Time of the Peak Power Plan. Tab – Power Management; The Wake-up Time of the devices in the Collection. Please let me know what you like and don't like about this script/ tool at: www.petervanderwoude.nl

I'm planning on making a screencast about this anytime soon... Until then, you can start the script with the following command line: PowerShell.exe -ExecutionPolicy ByPass .\ApprovalManager_v0_8p.ps1 -CollectiondId <CollectionId> - SiteCode <SiteCode> - SiteServer <SiteServer> - EnableAlert CollectionId - Specify the id of the collection, that contains the users, that the approver is allowed to approve, or deny, request of. SiteCode - Specify the site code of the ConfigMgr site. SiteServer - Specifify the site server name. EnableAlert - Specify this switch to enable alerts every hour

It uses the Network Access Account for starting the runbook(s), so make sure that the Network Access Account is member of the OrchestratorUser group.

But it is important to have your boundaries setup correct and configure protected DPs with that.

It's almost the same. Just don't give the deployment a schedule and make sure it's made available to either Only Configuration Manager Client, or Configuration Manager clients, media and PXE.

That's possible, just pay attention to overlapping boundaries and site assignment.

For downloading the updates it uses the internet connection of the device, on which you are running the console.

For downloading the updates it uses the internet connection of the device, on which you are running the console.

It's a bit more work, but yes, you can also utilize WMI and/or the registry. It can even be done by extending the Hardware Inventory with custom classes. The only down-side is, if you can even call it a down-side, it's not possible to show that information directly in the console. It can be used in queries and reports.

Is there still old information in the AD? Are the boundaries within CM12 not overlapping, or are there no overlapping boundaries between CM12 and CM07?

Multiple methods... One method is to create the application via the MSI and then afterward change the command line to whatever script you want to run (and does the installation plus the extra actions). Different methods are creating separate deployment types/ packages.

Have a look here about how to exclude files during the USMT capture: http://technet.microsoft.com/en-us/library/dd560762(v=ws.10).aspx

Also install MDT 2013 Preview and you should be fine.

That's only possible for Endpoint Protection Definition Updates. Otherwise you indeed have to start looking at things like Internet Clients, Direct Access, or GPO's.

To prevent issues (like phantom DPs/ Packages), I would always clean all the content that's on the DP.

Use the integration with MDT, then use a Gather -step and then you have a new variable AssetTag. See also: http://www.windows-noob.com/forums/index.php?/topic/1133-setting-computername-during-deployment/

Depends on what objects you want to migrate, see also: http://technet.microsoft.com/en-us/library/gg712307.aspx

Out-of-the-box there is nothing for ThinApp. Personally, I'm not very familiar with ThinApp, but when it's something that can be pushed to a client (via some sort of script, or command line), then it can also be done via ConfigMgr.

Either install some right-click tools and manage it from there, or create a package that kicks of a restart command.