Dell - Internal Use - Confidential Yes, its coming, but the links aren't posted yet.
Thanks, Warren From: [email protected] [mailto:[email protected]] On Behalf Of Denzik, Josh Sent: Tuesday, January 5, 2016 1:23 PM To: [email protected]; [email protected] Subject: [mssms] RE: New Dell Command | Integration Suite for System Center 2012 Is there documentation on how to setup the warranty stuff? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Giroux, Eric J Sent: Tuesday, January 5, 2016 12:46 PM To: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: New Dell Command | Integration Suite for System Center 2012 Does the 4.1 update fix the issue with some functionality not working when running from admin console on a workstation? I had an open case on this last year. The Command Configure BIOS package import would only work running the console on the site server as admin. Thanks, Eric From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of [email protected]<mailto:[email protected]> Sent: Tuesday, January 5, 2016 10:10 AM To: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Subject: [MDT-OSD] New Dell Command | Integration Suite for System Center 2012 This message originated outside of Unum. Use caution when opening attachments, clicking links or responding to requests for information. Dell - Internal Use - Confidential If you saw our demo at Ignite or MMS on automating all of your OSD drivers from within the SCCM console and are wondering when it will be available. It's here. http://en.community.dell.com/techcenter/enterprise-client/w/wiki/7533.dell-command-integration-suite-for-system-center As always, let me know what you love, hate, want changed, etc. Thanks, Warren Byle Dell | Business Client Systems Management Product Manager office +1 512 724 2626 [email protected]<mailto:[email protected]> Client Command Suite<http://dell.com/command> Join the conversation Twitter: WarrenByle<http://twitter.com/WarrenByle>
