Comments on: Export & share MDT Applications (New Tool)

By: diagg

diagg — Wed, 15 Sep 2010 22:03:31 +0000

Hello keith,
the tool is nice, but could be improved :

- would love to see a panel with “target deployment share” so i would not have to edit all scripts (aren’t computers created to make life easier)

- in the same direction : one script for all apps should be enough since we manually select all we want before proceeding…

Hope you are still developing the tool… as you said : the potential is great !

Diag

By: Phil

Phil — Wed, 18 Aug 2010 09:13:37 +0000

Hi Keith
Loved the idea of the app… I’m running a prooof on concept and wanted to import apps programatically between servers, rather than type all the details in over again, and found your app!

Sadly, I have an issue running it. I’m getting: Unhandled exception has occurred in your application…. Could not load file or assembly ‘System.Core. Version3.5.0.0 {some more data here} The system cannot find the file specified.

I realise that you’re not providing support, but if you have a pointer as to what I may have missed I’d be very much obliged.

I’m running Windoews Server 2008 SP2 32bit, with MDT 2010 Update1 (32bit) dated 02 July 2010.

Many thanks
Phil

By: CK

CK — Thu, 20 May 2010 13:09:22 +0000

The hiarchy folder checkboxes are not selectable.
Also errors on execution.

Great idea, but might need some fine tuning

By: Michael

Michael — Fri, 23 Apr 2010 09:31:43 +0000

If I select a application bundle I get an exeption.

System.ArgumentOutOfRangeException: startIndex cannot be larger than length of string.
Parameter name: startIndex
at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy)
at MDTApplicationExport.AppItem.GetShortName(PSObject Application)
at MDTApplicationExport.ExportApplications.ImportLineRecursive(PSObject Application, String RootsName)
at MDTApplicationExport.ExportApplications.ImportLineRecursive(PSObject Application, String RootsName)
at MDTApplicationExport.ExportApplications.ExportSingleApplication(PSObject Application)
at MDTApplicationExport.ExportApplications.ExportAppsRecursive(TreeNodeCollection Nodes)
at MDTApplicationExport.ExportApplications.ExportAppsRecursive(TreeNodeCollection Nodes)
at MDTApplicationExport.ExportApplications.ExportAppsRecursive(TreeNodeCollection Nodes)
at MDTApplicationExport.Form1.tabControl1_SelectedIndexChanged(Object sender, EventArgs e)
at System.Windows.Forms.TabControl.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.TabControl.WmSelChange()
at System.Windows.Forms.TabControl.set_SelectedIndex(Int32 value)
at MDTApplicationExport.Form1.NextB_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

By: keithga

keithga — Wed, 09 Dec 2009 20:28:53 +0000

Thanks!

Exporting apps from SMS/SCCM is a good idea. I’ll add it to my list of requested tools. Keep the ideas comming. :^)

By: Rliving

Rliving — Thu, 03 Dec 2009 08:22:57 +0000

Hi Keith,
Very nice tool! I like the application archive idea. I have a question related to packaged application sharing, but with a slightly different twist.

At my work, we have a requirement to use the same SMS (SMS 2003 SP3) packages to build the Base Reference Images as we use to deploy out to existing clients. With some Program variations on Imager versions, meaning ones where we do not want any of the normal daisy chained reboot or program install notifications to occur during the automated image build.

My question is, do you have a tool that could read the SMS db for a given ProgramID, and pull the install commands and source files (source files from a given SMS DP) for that program and any daisy chained programs. Then place that information into an imported able Applications XML (like what you’ve done here)? This would allow you to take advantage of the all the configuration and packaging effort that’s already done in SMS, within MDT and not have to Manually configure those SMS packaged applications.

Thoughts?

Thanks,
Roy