-
Posts
9181 -
Joined
-
Last visited
-
Days Won
366
Everything posted by anyweb
-
any reason you are not using Cu3 or even better, R2 ? does the media with the problem work on other hardware ?
- 2 replies
-
- SCCM 2012
- site-based
- (and 3 more)
-
you can set registry keys before or after the mbam client is installed to set the FVE settings in the registry this is because group policy cant be processed until after the task sequence is complete, once it is complete if any bitlocker actions are still required the mbam agent will popup within the 90 minutes period and prompt/inform the user the registry keys are the values that you set when setting your mbam options (group policy settings) i'll see if I can export them from a computer here and upload them for you
-
here's your problem <![LOG[Failed to run the action: Install Microsoft Office 2013 ProPlus. Download failed (Error: 87D00267; Source: CCM)]LOG]!><time="16:13:50.800+00" date="12-18-2013" component="TSManager" context="" type="3" thread="3036" file="instruction.cxx:895"> is it on the dp ? are you specifying any MP in the setup windows and configmgr step ?
-
How do I limit the list of Task Sequences shown?
anyweb replied to jgass0001's topic in Configuration Manager 2012
well you could create a collection query to limit the collection to All Unknown Computers but containing a query matching specific criteria... such as ip subnet, try it -
How do I limit the list of Task Sequences shown?
anyweb replied to jgass0001's topic in Configuration Manager 2012
simply create one collection for each location and deploy whatever task sequences you want to each collection -
interesting info, do you know what version the driver was (when crashing) and what prompted you to update it ?
-
you need to include the smsts.log file from your actual deployment, the error you quoted means as follows:- so you are trying to do something that is unsupported \ post the log and we'll take a look cheers niall
-
"MDMServer2012R2.konfig.local" <----- that might be your problem ! I had to rebuild my lab and use a 'real' FQDN to get things flowing so for example, my working Windows Intune+ConfigMgr lab has CM12 server has an FQDN of CM12.windowsintunenoob.com, the non-working Windows Intune+configmgr lab was sccm.server2008r2.lab.local I think .local FQDN's will cause problems with iOS, I had no success with iOS and .local in my first lab.
-
yup like so How can I password Protect a Task Sequence ? Password Protecting a Task Sequence