Peter van der Woude

Correct. A backup and restore needs the same server name. To point the clients to the new site, either push the client using the new site, or push a script using the old site to reassign the clients.

The site server in the DMZ doesn't have to be part of the same domain, it can also be part of a separate domain, specific to the DMZ. Installing a certificate on the site server in the DMZ can also be done manually.

Correct. For running something like a simple script it's still the best to use an old-school package.

The whole idea of using maintenance windows is to only install automatically during those windows. Depending on the configuration it's can still be possible to install the updates manually via Software Center, when available.

Yeah, it looks like it runs all the queries when the properties are opened. This seems to be be the WMI query: SELECT * FROM SMS_DPGroupContentInfo WHERE GroupID="". Another tip would be to look at the a WMI Explorer. This is an easy way to browse through WMI and find the properties that you need.

In this case, what do you mean by a secondary server? The console connects to the primary site (actually the sms provider), so assuming both of your consoles are connecting to the same I would guess that the problems is outside of ConfigMgr.

A good trick to start with is using the SMSProv.log file. That log file logs all the SMS Provider activity, which includes your actions through the console. So, open the log file and the console and open de content tab of a distribution group.

Web Application Proxy (WAP) is not going to help you in this scenario. It's simply not capable of providing a certificate.

IP Helpers are configured on your network devices, so the configuration depends completely on the brand and type of those devices. Often those vendors have clear documentation about the configuration of IP Helpers.

Check he execmgr.log for information about package intallations.

It struggling with the import of the ConfigMgr cmdlets. Are they available on the device that you're running the script on?

I would call it an impossible task to create an ADR to filter for an OOB patch. Personally, I wouldn't spent time on automating a task like that. It simply doesn't happen that often that it justice for automation. Like I mentioned before, I also wouldn't even want to automate a task like that. The only way to be in control of an action like that is to be on top of it.

Often that's related to issues with quotes (see also the comments of that article). If that's not the case, I would advise to post a comment with the article. It's easier troubleshooting by the person that created the script.

Use PowerShell and do something like this: http://configmgrblog.com/2013/01/25/how-to-cleanup-in-ad-deleted-devices-via-powershell-in-configmgr-2012-sp1/

The thing with OOB patches is that you don't know when they're coming, which makes it close to impossible to automate. Also, often these patches are released with a very high priority, which makes me want to be on top of it. That means I want to be sure that it happens and when it happens, so no ADR, but download and deploy them myself.

The "deployment time" -bug is only applicable to operating system deployments, so my guess would be the first Also, if it has something to do with deployment times then it should be fairly easy to reproduce.

That error is usually related to either the presence of the file or the file itself. It could be that the file is corrupted or there is something wrong in the XML.

Yes, you should be able to use the the Apple Configurator to create a configuration for your devices.

They're SQL queries. Given the fact that you had to ask that, I would strongly suggest to contact Microsoft before making that change. Another reason is that it's simply not supported to edit the database.

Yes, both the capture and the restore are supported on Windows 7.

Enhansoft has a tool that can do that. For more information please refer to: http://www.enhansoft.com/resources

AFAIK this won't work for iOS, yet, simply because there are no useable OMA-URIs available.

Well, to be quite honest, it can't be that difficult.... You can get cmdlets for membership rules to get the information and use the add cmdlets to add the membership rules. Those cmdlets are all described here: https://technet.microsoft.com/en-us/library/jj821831%28v=sc.20%29.aspx

If the task sequences are targeted at those devices, then yes. Nickolaj created a nice tool for that, see: http://www.scconfigmgr.com/2014/03/11/re-run-task-sequence-tool-1-0/

For Adobe updates SCUP is a good method, as Adobe delivers the CAB files for SCUP. In case you're also thinking about deploying other third-party updates, you also might want to look at addons to ConfigMgr for deploying third-party updates.