Might be, but that will have to be something Niehaus will have to answer. :)

Daniel Ratliff

From: [email protected] [mailto:[email protected]] On 
Behalf Of Roland Janus
Sent: Wednesday, December 04, 2013 12:04 PM
To: [email protected]
Subject: RE: [mssms] ConfigureConfigMgrIntegration.ps1 for MDT 2013 ?

I looked quickly into it before, didn't notice anything then, at least the 
paths look the same.
And it's also not failing anywhere and those copy steps would throw errors.

But doing it manually it states it connects to wmi and compiles a mof.
The 2012 script isn't doing that.

Is compiling the mof enough?

-


From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]]<mailto:[mailto:[email protected]]>
 On Behalf Of Daniel Ratliff
Sent: Mittwoch, 4. Dezember 2013 17:46
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] ConfigureConfigMgrIntegration.ps1 for MDT 2013 ?

That script looks easy enough. Here's a few things to check. I don't have MDT 
2013 installed right now or I would check myself.

Verify the MDT path in the registry exists in MDT 2013
$mdtPath = (get-itemproperty "hklm:\Software\Microsoft\Deployment 4" -name 
Install_Dir -ErrorAction SilentlyContinue).Install_Dir

Verify the ConfigMgr console is the same
$cm12Path = (get-itemproperty "hklm:\Software\Microsoft\ConfigMgr10\Setup" 
-name "UI Installation Directory" -ErrorAction SilentlyContinue).'UI 
Installation Directory'
$cm12Path = (get-itemproperty 
"hklm:\Software\wow6432node\Microsoft\ConfigMgr10\Setup" -name "UI Installation 
Directory" -ErrorAction SilentlyContinue).'UI

Check the ConfigMgr path so the extensions can be added
    # Copy needed DLLs
    Copy-Item -Path "$mdtPath\Bin\Microsoft.BDD.CM12Actions.dll" -Destination 
"$cm12Path\Bin\Microsoft.BDD.CM12Actions.dll" -Force
    Copy-Item -Path "$mdtPath\Bin\Microsoft.BDD.Workbench.dll" -Destination 
"$cm12Path\Bin\Microsoft.BDD.Workbench.dll" -Force
    Copy-Item -Path "$mdtPath\Bin\Microsoft.BDD.ConfigManager.dll" -Destination 
"$cm12Path\Bin\Microsoft.BDD.ConfigManager.dll" -Force
    Copy-Item -Path "$mdtPath\Bin\Microsoft.BDD.CM12Wizards.dll" -Destination 
"$cm12Path\Bin\Microsoft.BDD.CM12Wizards.dll" -Force
    Copy-Item -Path "$mdtPath\Bin\Microsoft.BDD.PSSnapIn.dll" -Destination 
"$cm12Path\Bin\Microsoft.BDD.PSSnapIn.dll" -Force
    Copy-Item -Path "$mdtPath\Bin\Microsoft.BDD.Core.dll" -Destination 
"$cm12Path\Bin\Microsoft.BDD.Core.dll" -Force

   # Copy extensions folder
    Copy-Item -Path "$mdtPath\Templates\CM12Extensions" -Destination 
"$cm12Path\XmlStorage\Extensions" -Force -Recurse

Daniel Ratliff

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Roland Janus
Sent: Wednesday, December 04, 2013 11:23 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] ConfigureConfigMgrIntegration.ps1 for MDT 2013 ?

Doesn't look like, they are all MDT specific (from the module), not about 
integrating

-R


From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]]<mailto:[mailto:[email protected]]>
 On Behalf Of Roland Janus
Sent: Mittwoch, 4. Dezember 2013 17:15
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] ConfigureConfigMgrIntegration.ps1 for MDT 2013 ?

Build by Michael.

I'm checking that :)

Thanks, roland


From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Daniel Ratliff
Sent: Mittwoch, 4. Dezember 2013 16:39
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] ConfigureConfigMgrIntegration.ps1 for MDT 2013 ?

Is that the build in MDT PowerShell script or a custom one Michael put together?

I think 2013 has built in PoSH scripts to integrate now?

Daniel Ratliff

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Roland Janus
Sent: Wednesday, December 04, 2013 10:36 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] ConfigureConfigMgrIntegration.ps1 for MDT 2013 ?

None, it's not just doing anything, or expected, like enabling integration. :)
When starting integration manually it works.

-R


From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]]<mailto:[mailto:[email protected]]>
 On Behalf Of 
[email protected]<mailto:[email protected]>
Sent: Mittwoch, 4. Dezember 2013 15:52
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] ConfigureConfigMgrIntegration.ps1 for MDT 2013 ?

What error do you see?



Christopher Catlett
Consultant | Detroit
[MCTS_2013_small]

Sogeti USA
Office 248-876-9738 |Fax 877.406.9647
26957 Northwestern Highway, Suite 130, Southfield, MI 48033-8456
www.us.sogeti.com<http://www.us.sogeti.com/>

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Roland Janus
Sent: Wednesday, December 04, 2013 9:22 AM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] ConfigureConfigMgrIntegration.ps1 for MDT 2013 ?

The script for MDT2012 isn't working on 2013. Is there an update Michael? :)

-R





The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information 
in error,
please contact the sender and delete or destroy the material/information.




The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information 
in error,
please contact the sender and delete or destroy the material/information.



The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material.  If you receive this 
material/information in error,
please contact the sender and delete or destroy the material/information.


<<inline: image001.jpg>>

Reply via email to