1E Free Tools - SMS / ConfigMgr 2007

Program Clone Wizard

The Program Clone Wizard is an MMC snap-in for the Administrator Console. It extends the right mouse click menu for a single SMS/ConfigMgr Program allowing you to run a simple wizard which duplicates the Program and sets it to run using Nomad Enterprise.

Date: 16 Aug 2006   Size: 234 Kb

Program Clone Script

This download contains a vb script which allows you to make a copy of an existing SMS/ConfigMgr Program which is configured to use Nomad Enterprise. This automates the task of converting your existing SMS/ConfigMgr Programs to use Nomad Enterprise.

Date: 08 Aug 2006   Size: 8.62 Kb

LogfileViewer

Easily monitor and investigate multiple log files in a single consolidated view. This free tool allows you to compare log file entries from different files side-by-side. It supports the following features: multiple file sets; file and entry highlighting; date and time management and sorting and filtering.

Date: 24 Oct 2005   Size: 276 Kb

Program Pre-pend Script

This download contains a sample vb script which allows you to pre-pend your existing SMS/ConfigMgr Program command lines with the text "SMSNomad.exe". This automates the task of converting your existing SMS/ConfigMgr Programs to using Nomad Enterprise.

Date: 03 Sep 2005   Size: 7.26 Kb

SMSOrganiser

SMSOrganiser is a free tool from 1E for Microsoft SMS 2003 SP1. This handy tool enables you to easily drag and drop your SMS Packages into folders using a simple user interface. This product requires SMS 2003 SP1.

Date: 04 May 2005   Size: 46.7 Kb

ProgEditor

ProgEditor is a utility that can be used to edit SMS Programs command lines and attributes. The utility gives you a better view when the command line is very long.

Date: 06 Apr 2005   Size: 75.7 Kb

Client Master

A simple SMS 2.0 client installation method run from the SMS Central site using existing Network Discovery information. For Windows NT/2000.

Date: 02 Feb 2005   Size: 823 Kb

SMS Advert Success Rate Reporting

Generates ‘Snap-shot’ reports in Excel of the success rate of SMS Advertisement.

Date: 12 Jan 2005   Size: 484 Kb

User Coll

A command line SMS tool for creating a new user collection from a text file.

Date: 20 Aug 2004   Size: 78.7 Kb

SMSDependency

Tracing a chain of dependencies for programs in SMS can be a time consuming business. SMSDependency solves this usability issue by providing visibility of the entire tree of dependencies for a given program in one place.

Date: 21 Jul 2004   Size: 300 Kb

SMS Commander

SMSCommander is an extension for the SMS Administrator Console. It allows you to dynamically run command lines against SMS Resources. Setup these command lines in an ini file and use System Properties as input parameters.

Date: 10 Jun 2004   Size: 444 Kb

WMIPing

This is a simple tool for administrators to diagnose if connection to WMI of the target system can be established.

Date: 12 Sep 2003   Size: 65.9 Kb

EasyMSI

An extension to the SMS Administrator Console which enables easy deployment and maintenance of software to single machines using Windows Installer (MSI)

Date: 18 Aug 2003   Size: 508 Kb

User Info

A tool which provides a way of returning custom data to SMS. In this sample, the user's postcode and location are requested. This can be easily altered to return any custom information.

Date: 23 Jun 2003   Size: 6.14 Kb

Client Builder

A simple SMS 2.0 client Installation method run from the client. It is a command line tool which removes and re-installs SMS client components. It can be used to repair faulty client Installation or can be integrated easily into any unattended build or ghosting process. For Windows NT/2000.

Date: 17 Mar 2003   Size: 122 Kb

MSIMaster

MSIMaster enhances the SMS product by making Windows Installer product information available within the SMS database. This information adds to the standard Systems Management Server software inventory.

Date: 17 Mar 2003   Size: 208 Kb

SMS Program Wrapper

When deploying software when users may be logged in, SMS Program Wrapper displays a fully customisable dialog box prior to deployment, checks for open applications and provides customisable status MIF handling.

1E Free Tools for ConfigMgr 2007

ConfigMgr tools

Advanced Task Sequence Environment Tool

The TSEnv2.exe is a command line tool that lets administrators manipulate the Microsoft 2007 task sequence environment. It allows them to get, set, list and dump all variables within the OSD Task Sequence environment. This tool also allows changes to ‘read only’ variables that cannot be changed with the original TSEnv.exe which is included in the Configuration Manager 2007 OSD environment.

Date: 11 May 2009   Size: 108 Kb

1E Migration Tool

This tool is designed to allow an SMS Administrator to Migrate all or selected packages and programs from his SMS environment into a System Center Configuration Management (ConfigMgr) environment. The tool has the following features:-

• The Migration of Package and Program details along with source files
• Renaming of Package and Program names during migration
• Direct transfer of packages from your SMS site to ConfigMgr
• Export to flat file structure from SMS site and Import into ConfigMgr from flat file
• Exporting of SMSNomad command line settings to new ConfigMgr Nomad tab settings.

Date: 23 Feb 2009   Size: 107 Kb

Service Window

Provides a graphical interface that allows an administrative user to view, add, edit and delete maintenance windows (service windows) on a selected target computer. Maintenance windows define times during which Microsoft System Center Configuration Manager 2007(ConfigMgr) can apply advertisements and software update deployments to the specified computer.
If no windows are specified then the computer can receive advertisements at any time. Administrators may assign advertisements outside any maintenance windows irrespective of what has been set.

Date: 23 Dec 2008   Size: 110 Kb

WMI Permissions Tool

The WMIConfigPerms.exe is a command line to that lets you view and edit the security of a specified WMI Namespace. This tool will allow administrators to silently configure namespaces in preparation for software installs that require modified permissions to install. Examples are configuring permissions for the SMS Admins group on Root\SMS; 1E Shopping service account on Root\SMS; non-administrators on SQL Reporting Services; 1E NightWatchman Console service account on the N1E\WakeUp and SMSWAK namespaces.

Date: 12 Apr 2010   Size: 60.1 Kb

Access to SQL Query Build automatically

MMS 2011 SPONSORS & EXHIBITORS

MMS 2011 SPONSORS & EXHIBITORS

We would like to thank the following sponsors and exhibitors for their part in making MMS 2011 a success.

Table of Contents

Platinum Sponsors

Dell develops and delivers a comprehensive portfolio of IT services and solutions that reduce IT complexity and lower costs. We take a holistic view of each customer’s environment and business objectives to design solutions that help enable growth, streamline operations, and show a measurable return on investment. Our tested and proven solutions help meet specific business goals while mitigating risk. We offer interrelated consulting, business process, applications, infrastructure, and managed services that consistently deliver deep levels of value for our customers in commercial enterprises, healthcare, government, and education.
www.dell.com

---

As a world-leading information technology company, HP applies new thinking and ideas to create more simple, valuable and trusted experiences with technology. Our focus is to continuously improve the way our customers live and work through technology products and services, form the individual consumer to the largest enterprise. More information can be found at www.hp.com.
www.hp.com

Gold Sponsors

1E believes that all organizations should expect more from their IT. Founded in 1997, 1E pioneered advanced PC power management with the release of NightWatchman^® and WakeUp^™ as part of a unique range of industry-leading solutions designed to reduce IT costs. Headquartered in London and New York with nearly 14m licenses deployed worldwide, over 1100 public and private sector organizations in 42 countries enlist 1E to help them work more efficiently, productively and sustainably.  1E solutions have cumulatively saved  $530m+ in energy costs alone, cutting CO2 emissions by 4.3 million US tons. For more information, please visit: www.1e.com.
www.1e.com

---

Adaptiva^™, a Microsoft Gold Partner, and System Center Alliance member, makes sophisticated add-ons for Microsoft’s Configuration Manager product. Based on cutting edge technology, Adaptiva's OneSite, Client Health, SCCM Companion, and Green Planet products are deployed at leading Fortune 500 companies, federal and state government agencies, and Department of Defense customers. These products reduce infrastructure costs, increase desktop manageability, and empower administrators with robust Systems Management capabilities. Adaptiva has earned a legendary reputation for lightning-fast support, extreme scalability, and rich enterprise feature sets which have led to successful deployments on large 200,000+ node networks.
www.adaptiva.com

---

AppSense has been providing technology solutions to optimize the user experience and simplify desktop management for over ten years, and has developed the technology, experience and operational capacity to offer a solution to what has been to date the most challenging yet important aspect of the Microsoft desktop to manage - the user.  Whether using physical PC, virtual desktops, App-V delivered applications, client hypervisors, cloud-based infrastructures or combinations thereof, AppSense User Virtualization technology provides a seamless working experience to all users at all times. AppSense is a Microsoft Gold Partner and is the only provider of user personalization technology in global VDI solutions from IBM, Dell, HP and CSC.
www.appsense.com

---

Citrix Systems, Inc. (NASDAQ:CTXS) is a leading provider of virtual computing solutions that help companies deliver IT as an on-demand service. Founded in 1989, Citrix combines virtualization, networking, and cloud computing technologies into a full portfolio of products that enable virtual workstyles for users and virtual datacenters for IT.  More than 230,000 organizations worldwide rely on Citrix to help them build simpler and more cost-effective IT environments. Citrix partners with over 10,000 companies in more than 100 countries. Annual revenue in 2010 was $1.87 billion. Visit us at booth #315 and follow us at http://twitter.com/citrixmicrosoft.
www.citrix.com

---

EMC Corporation (NYSE: EMC) is the world’s leading developer and provider of information infrastructure technologies. We provide global customers—of all sizes and across all industries—the products, services, and solutions they need to manage data growth and get the most value from their information. EMC leads customers on the journey to the private cloud—a dramatically more efficient and flexible way to manage, deliver, and consume IT services for reduced costs and increased business agility. EMC is a Microsoft Gold Certified Partner with 15 certifications and recognized 20-time Partner of the Year winner.
www.emc.com

---

For over 40 years Intel has been bringing new technology to the marketplace. Now we are building on our historical strength in silicon innovation and global manufacturing capacity to create new products and technologies that help people live happier, more productive lives. It's not just about making technology faster, smarter and cheaper - it's about using that technology to make life better, richer, and more convenient for everyone. Intel provides resources, technologies, products and services that both IT professionals and developers need to create innovative products and industry-leading software solutions with enhanced business value. Additional information available at www.intelalliance.com/microsoft.
www.intelalliance.com/microsoft

---

NetApp creates innovative storage and data management solutions that deliver outstanding cost efficiency and accelerate performance breakthroughs. Our dedication to principles of simplicity, innovation, and customer success has made us one of the fastest-growing storage and data management providers today.  Customers around the world choose us for our “go beyond” approach and broad portfolio of solutions for server-to-storage virtualization, business applications, data protection, and more. Our solutions provide nonstop availability of critical business data and simplify business processes so you can deploy new capabilities with confidence and get to revenue faster than ever before. Discover our passion for helping companies around the world go further, faster at www.netapp.com.
www.netapp.com

---

RES Software, the proven leader in dynamic desktop solutions, is driving a transformation in the way organizations manage, maintain and reduce the cost of their desktop infrastructure. The RES Software award-winning, patented products enable IT professionals to manage and deliver secure, personalized and compliant desktops independent of the underlying computing infrastructure – thin clients, virtual desktops, physical desktops, or server-based computing environments. The company empowers customers, from small to medium-sized businesses to global enterprises, to reduce desktop complexity and meet the essential needs of a dynamic workforce that requires on-demand access to their personalized workspaces. For more information, follow updates on Twitter @RESSoftware and visit www.ressoftware.com.
www.ressoftware.com

---

SCCM Expert is a Microsoft Gold Partner and founding member of the Microsoft System Center Alliance. SCCM Expert’s Self Service deeply integrates with System Center Configuration Manager 2007^® enabling an automated software request and license management business process.

appSurvey, in Self Service, automates application migration work flow for large scale Windows 7 migrations. Administrators approve and trigger remote migration based on end-user surveys. We help global corporations, education institutions and government agencies:

• Boost productivity through on-demand application delivery
• Simplify Windows7 application migration
• Save IT time by automating software request management
• Reduce license spend through leasing and reclamation

www.sccmexpert.com

---

Veeam Software, 2010 Microsoft Partner of the Year finalist, develops innovative software for managing virtual datacenter environments. Veeam is an active member of the System Center Alliance with solutions complementing Microsoft Core Infrastructure Optimization offerings. Veeam’s PRO-enabled nworks Management Pack provides well-informed monitoring of VMware from within Operations Manager, and integrates with SCVMM to automate administrative and remedial actions. The Management Pack is verified as “VMware Ready” on vSphere4 and VI3, and it is part of Veeam ONE, which provides a single solution to optimize the performance, configuration and utilization of growing, mission-critical virtual infrastructures.
www.veeam.com

Bronze Sponsors

www.app-dna.com

---

Avanade business technology services connect insight, innovation and expertise in Microsoft^® technologies to help customers realize results. Avanade’s services and solutions help improve performance, productivity and sales for organizations in all industries. The company applies Microsoft expertise from its global network of consultants, who help deliver results faster, at lower cost and with less risk. Avanade, founded in 2000 by Accenture and Microsoft Corporation, has more than 11,000 dedicated resources in more than 24 countries.
www.avanade.com

---

Bay Dynamics, a leading analytics technology provider in the systems management and security space, brings business intelligence and cube-based analytics to System Center products. Bay Dynamics has created proven and highly adopted solutions that provide detailed insight into IT operations through trend discovery and powerful forensic analysis capabilities. This allows Bay Dynamics’ clients greater visibility into their environment to help them plan for the future. Through IT Analytics^™ for System Center, companies can now turn their vast amounts of data coming from System Center products into useful information that will help them identify problems, view trends, and make more informed and timely business decisions.
www.baydynamics.com

---

CommVault^® Simpana's^® Windows Centric Data Management software enables an organization to granularly and content search heterogeneous data. Meet with, see live demos and talk with CommVault technical experts about how one solution enables backup, recovery, archiving, compliance, deduplication, search, snapshot management, replication, SRM and reporting. For a preview, visit www.commvault.com/microsoft and learn how the Microsoft Office Products team benefitted from CommVault.
www.commvault.com

---

It can be complicated to manage PCs and their users with Microsoft System Center Configuration Manager (SCCM), and therefore daily operational tasks often need involvement from the SCCM Manager. With easy administration suite, which is a superstructure to SCCM, you will be able to let any IT employee carry out up to 90% of the daily SCCM tasks.
www.easyadm.com

---

Iron Mountain provides information management services that help businesses lower the costs, risks and inefficiencies of managing their physical and digital data. The company’s solutions enable customers to protect and better use their information — regardless of its format, location or lifecycle stage — so they can optimize their business and ensure proper recovery, compliance and discovery. Founded in 1951, Iron Mountain manages billions of information assets for businesses around the world. For more information, visit www.ironmountain.com
www.ironmountain.com

---

NetWrix Corporation provides systems management solutions for change auditing, regulatory compliance, identity management, security, endpoint management, health monitoring, virtualization, SharePoint, and others. The company offers simple and affordable products for a fraction of the price of similar competitive offerings, and matches its quality products with reliable customer service. Please visit the NetWrix booth on MMS to see how the award-winning NetWrix products can extend Microsoft System Center family and help you manage your IT infrastructure efficiently and sustain compliance.
www.netwrix.com

---

Odyssey Software is a leading provider of enterprise-class remote device management software products that make it efficient and cost effective for IT organizations to manage and support the complexity of remote (mobile and embedded) deployments utilizing today’s most popular devices, including Windows Phone 7. Our flagship product, Athena, is the only mobile device management software that seamlessly integrates into Configuration Manager 2007, providing vital functions for management and support of remote devices. 
www.odysseysoftware.com

---

The Provance^™ IT Asset Management Pack for Microsoft^® System Center Service Manager provides powerful IT Asset Life Cycle Management and Software Asset Management that drives down IT costs, increases service management efficiency, and reduces risk. Supporting ITIL^® and the Microsoft Operations Framework, Provance strengthens IT effectiveness of companies at every level of the Microsoft Core Infrastructure Optimization model. Provance is a Microsoft Gold Certified Partner with the Systems Management Competency, and System Center Alliance Member.
www.provance.com

---

Quest Software simplifies and reduces the cost of managing IT for more than 100,000 customers worldwide. Our innovative solutions make solving the toughest IT management problems easier, enabling customers to save time and money across physical, virtual and cloud environments.  For more information about Quest go to www.quest.com.
www.quest.com

---

Simplify the deployment and management of Microsoft System Center management packs, configuration packs and configuration compliance reporting with Silect’s MP Studio (for Operations Manager), CP Studio (for Configuration Manager/DCM) and ConfigWise. With Silect, you gain the expertise to quickly and easily customize and optimize key System Center components for enhanced reliability and faster ROI.  Learn how you can overcome complexity, speed implementation, minimize risk and increase productivity across your System Center environment by visiting www.silect.com.
www.silect.com

---

WinWorkers is an international IT corporation headquartered in Switzerland. As system integrator in the MS System Center environment WinWorkers focuses on corporate automation and deployment projects in Germany, Austria, Switzerland, the US and the UK. WinWorkers also develops software solutions in-house that are used and implemented world-wide. Since March 2010 WinWorkers is a member of the Microsoft System Center Alliance Group of. It is the first enterprise in the D-A-CH area to gain this award.
www.winworkers.com

---

Redmond magazine provides cutting-edge product, business and how-to information for network professionals, IT managers and IT directors working on the Microsoft Windows platform. Visit our web site for news, analysis, trends, product reviews, roadmaps and best practices. Our readers trust our independent stance on Microsoft, the Windows computing platform and third-party vendors. They come for product information, business strategies and behind-the-scenes insight so they can make better informed decisions for their IT infrastructures.
redmondmag.com

---

The Windows IT Pro community is the heartbeat of the Windows IT world – a gathering of people, content, and resources focused on Microsoft Windows technologies and applications. It's a community bringing an independent, uncensored voice to IT managers, network and systems administrators, developers, systems analysts, CIOs, CTOs, and other technologists at companies worldwide. The Windows IT Pro community is marked by its depth of editorial content that allows IT professionals to interact with colleagues, technical experts, analysts, and other thought-leaders.
www.windowsitpro.com

Patching Related End to end – Collections and reports :-

Below is for a compliance report based on SQL

declare @CollectID AS  varchar(8)
SET @CollectID= 'SMS0001'

declare @CollectionListID AS  varchar(90)
SET @CollectionListID='ScopeId_5432f432-F885-4A98-B666-5432134122/AuthList_F15C63EA-B655-4940-A250-654323fd432'

declare @CI_ID int; select @CI_ID=CI_ID from v_ConfigurationItems where CIType_ID=9 and CI_UniqueID=@CollectionListID

declare @CollCount int, @NumClients int; select @CollCount = count(*), @NumClients=isnull(sum(cast(IsClient as int)), 0)

from v_ClientCollectionMembers ccm where ccm.CollectionID=@CollectID

select
    CollectionName=vc.Name,
    'Update List'=al.Title,
    Status=sn.StateName,
    NumberOfComputers=count(*),
    PComputers=convert(numeric(5,2), (isnull(count(*), 0)* 100.00 / isnull(nullif(@CollCount, 0), 1))),
    CollectionID=@CollectID,
    AuthListID=@CollectionListID
from v_Collection vc right join v_ClientCollectionMembers cm on vc.CollectionID=cm.CollectionID
join v_UpdateListStatus_Live cs on cs.CI_ID=@CI_ID and cs.ResourceID=cm.ResourceID
left join v_StateNames sn on sn.TopicType=300 and sn.StateID=isnull(cs.Status, 0)
left join v_AuthListInfo al on cs.CI_ID=al.CI_ID
where cm.CollectionID=@CollectID
group by vc.Name, sn.StateName, al.Title
order by sn.StateName

________________________________________________________________________________________________________________________
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
________________________________________________________________________________________________________________________
<<<<<<<---WQL based query----->>>>> systems will be automatically part of the collection with the name of "2011 Jan Updates" Deployment

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System  WHERE        SMS_R_System.ResourceID IN (     SELECT        SMS_UpdateComplianceStatus.MachineID        FROM         SMS_UpdateComplianceStatus        JOIN SMS_UpdateDeploymentSummary           ON    SMS_UpdateComplianceStatus.CI_ID = SMS_UpdateDeploymentSummary.CI_ID     WHERE           SMS_UpdateComplianceStatus.Status = "2"        AND SMS_UpdateDeploymentSummary.AssignmentName    = "2011 Jan Updates")

______________________________________________________________________________________________________________________________
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
______________________________________________________________________________________________________________________________

Patching Related End to end – Collections and reports :-

Public SCCM 2007 Right Click Tools : TWO different versions available

One from Dan Ireland

http://myitforum.com/cs2/blogs/direland/pages/sccm-console-extensions.aspx

Second One from Rick Houchins

 

http://myitforum.com/cs2/blogs/rhouchins/0401ConfigMgrTools.zip

AutoCAD Mof File for all versions

:::::::::::::::SMS_def.mof file:::::::::::::::

#pragma namespace ("\\\\.\\root\\cimv2\\sms")

[ SMS_Report (TRUE),
SMS_Group_Name ("AutoCAD 14"),
SMS_Class_ID ("CUSTOM|AUTOCAD_14|1.0") ]
class Win32Reg_AutoCAD_14 : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Release;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string StandaloneNetworkType;
};

[ SMS_Report (TRUE),
SMS_Group_Name ("AutoCAD 2000"),
SMS_Class_ID ("CUSTOM|AUTOCAD_2000|1.0") ]
class Win32Reg_AutoCAD_2000 : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Release;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string StandaloneNetworkType;
};

[ SMS_Report (TRUE),
SMS_Group_Name ("AutoCAD 2000i"),
SMS_Class_ID ("CUSTOM|AUTOCAD_2000i|1.0") ]
class Win32Reg_AutoCAD_2000i : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Release;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string StandaloneNetworkType;
};

[ SMS_Report (TRUE),
SMS_Group_Name ("AutoCAD 2002"),
SMS_Class_ID ("CUSTOM|AUTOCAD_2002|1.0") ]
class Win32Reg_AutoCAD_2002 : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Release;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string StandaloneNetworkType;
};

[ SMS_Report (TRUE),
SMS_Group_Name ("AutoCAD 2004"),
SMS_Class_ID ("CUSTOM|AUTOCAD_2004|1.0") ]
class Win32Reg_AutoCAD_2004 : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Release;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string StandaloneNetworkType;
};

[ SMS_Report (TRUE),
SMS_Group_Name ("AutoCAD 2005"),
SMS_Class_ID ("CUSTOM|AUTOCAD_2005|1.0") ]
class Win32Reg_AutoCAD_2005 : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Release;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string StandaloneNetworkType;
};

[ SMS_Report (TRUE),
SMS_Group_Name ("AutoCAD 2006"),
SMS_Class_ID ("CUSTOM|AUTOCAD_2006|1.0") ]
class Win32Reg_AutoCAD_2006 : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Release;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string StandaloneNetworkType;
};

[ SMS_Report (TRUE),
SMS_Group_Name ("AutoCAD 2007"),
SMS_Class_ID ("CUSTOM|AUTOCAD_2007|1.0") ]
class Win32Reg_AutoCAD_2007 : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Release;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string StandaloneNetworkType;
};

[ SMS_Report (TRUE),
SMS_Group_Name ("AutoCAD 2008"),
SMS_Class_ID ("CUSTOM|AUTOCAD_2008|1.0") ]
class Win32Reg_AutoCAD_2008 : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Release;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string StandaloneNetworkType;
};

[ SMS_Report (TRUE),
SMS_Group_Name ("AutoCAD 2009"),
SMS_Class_ID ("CUSTOM|AUTOCAD_2009|1.0") ]
class Win32Reg_AutoCAD_2009 : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Release;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string StandaloneNetworkType;
};

[ SMS_Report (TRUE),
SMS_Group_Name ("AutoCAD 2010"),
SMS_Class_ID ("CUSTOM|AUTOCAD_2010|1.0") ]
class Win32Reg_AutoCAD_2010 : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Release;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string StandaloneNetworkType;
};

[ SMS_Report (TRUE),
SMS_Group_Name ("AutoCAD 2011"),
SMS_Class_ID ("CUSTOM|AUTOCAD_2011|1.0") ]
class Win32Reg_AutoCAD_2011 : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Release;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string StandaloneNetworkType;
};

[SMS_Report(TRUE),SMS_Group_Name("AutoCAD 2012"),SMS_Class_ID("Custom|Autocad_2012|1.0"),
SMS_Context_1("__ProviderArchitecture=32|uint32"),
SMS_Context_2("__RequiredArchitecture=true|boolean")]
Class Win32Reg_Autocad_2012: SMS_Class_Template
{
[SMS_Report(TRUE),key] string KeyName;
[SMS_Report(TRUE)] String ProductName;
[SMS_Report(TRUE)] String Release;
[SMS_Report(TRUE)] String SerialNumber;
[SMS_Report(TRUE)] String StandaloneNetworkType;
};

[SMS_Report(TRUE),SMS_Group_Name("AutoCAD 2012"),SMS_Class_ID("Custom|Autocad_2012|1.0"),
SMS_Context_1("__ProviderArchitecture=64|uint32"),
SMS_Context_2("__RequiredArchitecture=true|boolean")]
Class Win32Reg_Autocad_2012_64 : SMS_Class_Template
{
[SMS_Report(TRUE),key] string KeyName;
[SMS_Report(TRUE)] String ProductName;
[SMS_Report(TRUE)] String Release;
[SMS_Report(TRUE)] String SerialNumber;
[SMS_Report(TRUE)] String StandaloneNetworkType;
};

//***************************************
//* AutoCAD LT Starts Here
//***************************************

[ SMS_Report (TRUE),
SMS_Group_Name ("AutoCAD LT 97"),
SMS_Class_ID ("CUSTOM|AUTOCAD_LT_97|1.0") ]
class Win32Reg_AutoCAD_LT_97 : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Release;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string StandaloneNetworkType;
};

[ SMS_Report (TRUE),
SMS_Group_Name ("AutoCAD LT 2000"),
SMS_Class_ID ("CUSTOM|AUTOCAD_LT_2000|1.0") ]
class Win32Reg_AutoCAD_LT_2000 : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Release;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string StandaloneNetworkType;
};

[ SMS_Report (TRUE),
SMS_Group_Name ("AutoCAD LT 2000i"),
SMS_Class_ID ("CUSTOM|AUTOCAD_LT_2000i|1.0") ]
class Win32Reg_AutoCAD_LT_2000i : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Release;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string StandaloneNetworkType;
};

[ SMS_Report (TRUE),
SMS_Group_Name ("AutoCAD LT 2002"),
SMS_Class_ID ("CUSTOM|AUTOCAD_LT_2002|1.0") ]
class Win32Reg_AutoCAD_LT_2002 : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Release;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string StandaloneNetworkType;
};

[ SMS_Report (TRUE),
SMS_Group_Name ("AutoCAD LT 2004"),
SMS_Class_ID ("CUSTOM|AUTOCAD_LT_2004|1.0") ]
class Win32Reg_AutoCAD_LT_2004 : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Release;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string StandaloneNetworkType;
};

[ SMS_Report (TRUE),
SMS_Group_Name ("AutoCAD LT 2005"),
SMS_Class_ID ("CUSTOM|AUTOCAD_LT_2005|1.0") ]
class Win32Reg_AutoCAD_LT_2005 : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Release;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string StandaloneNetworkType;
};

[ SMS_Report (TRUE),
SMS_Group_Name ("AutoCAD LT 2006"),
SMS_Class_ID ("CUSTOM|AUTOCAD_LT_2006|1.0") ]
class Win32Reg_AutoCAD_LT_2006 : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Release;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string StandaloneNetworkType;
};

[ SMS_Report (TRUE),
SMS_Group_Name ("AutoCAD LT 2007"),
SMS_Class_ID ("CUSTOM|AUTOCAD_LT_2007|1.0") ]
class Win32Reg_AutoCAD_LT_2007 : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Release;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string StandaloneNetworkType;
};

[ SMS_Report (TRUE),
SMS_Group_Name ("AutoCAD LT 2008"),
SMS_Class_ID ("CUSTOM|AUTOCAD_LT_2008|1.0") ]
class Win32Reg_AutoCAD_LT_2008 : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Release;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string StandaloneNetworkType;
};

[ SMS_Report (TRUE),
SMS_Group_Name ("AutoCAD LT 2009"),
SMS_Class_ID ("CUSTOM|AUTOCAD_LT_2009|1.0") ]
class Win32Reg_AutoCAD_LT_2009 : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Release;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string StandaloneNetworkType;
};

[ SMS_Report (TRUE),
SMS_Group_Name ("AutoCAD LT 2010"),
SMS_Class_ID ("CUSTOM|AUTOCAD_LT_2010|1.0") ]
class Win32Reg_AutoCAD_LT_2010 : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Release;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string StandaloneNetworkType;
};

[ SMS_Report (TRUE),
SMS_Group_Name ("AutoCAD LT 2011"),
SMS_Class_ID ("CUSTOM|AUTOCAD_LT_2011|1.0") ]
class Win32Reg_AutoCAD_LT_2011 : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Release;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string StandaloneNetworkType;
};

//***************************************
//* Inventor Starts Here
//***************************************

[ SMS_Report (TRUE),
SMS_Group_Name ("Inventor"),
SMS_Class_ID ("CUSTOM|AUTODESK_INVENTOR|1.0") ]
class Win32Reg_Autodesk_Inventor : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Release;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string StandaloneNetworkType;
};

//***************************************
//* 3dsmax Starts Here
//***************************************

[ SMS_Report (TRUE),
SMS_Group_Name ("3dsmax 9"),
SMS_Class_ID ("CUSTOM|3dsmax_9|1.0") ]
class Win32Reg_3dsmax_9 : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Release;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string StandaloneNetworkType;
};

[ SMS_Report (TRUE),
SMS_Group_Name ("3dsmax 13"),
SMS_Class_ID ("CUSTOM|3dsmax_13|1.0") ]
class Win32Reg_3dsmax_13 : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Release;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string StandaloneNetworkType;
};

[ SMS_Report (TRUE),
SMS_Group_Name ("3dsmax 14"),
SMS_Class_ID ("CUSTOM|3dsmax_14|1.0") ]
class Win32Reg_3dsmax_14 : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Release;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string StandaloneNetworkType;
};

//********************
//Algor Starts here
//**********************

[ SMS_Report (TRUE),
SMS_Group_Name ("Algor"),
SMS_Class_ID ("CUSTOM|Algor_All|1.0") ]
class Win32Reg_Algor : SMS_Class_Template
{
    [SMS_Report (TRUE), Key ] string KeyName;
    [SMS_Report (TRUE)] string ProductName;
    [SMS_Report (TRUE)] string Version;
    [SMS_Report (TRUE)] string SerialNumber;
    [SMS_Report (TRUE)] string InstallationType;
};

:::::Configuration.mof file:::::

 

#pragma namespace("\\\\.\\root\\cimv2")

//***************************************
//* AutoCAD Starts Here
//***************************************

// AutoCAD 14
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\AutoCAD\\R14.0")
]

class Win32Reg_AutoCAD_14
{
    [Key] string KeyName;
    [PropertyContext("ProductName")] string ProductName;
    [PropertyContext("Release")] string Release;
    [PropertyContext("SerialNumber")] string SerialNumber;
    [PropertyContext("StandaloneNetworkType")] string StandaloneNetworkType;
};

// AutoCAD 2000
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\AutoCAD\\R15.0")
]

class Win32Reg_AutoCAD_2000
{
    [Key] string KeyName;
    [PropertyContext("ProductName")] string ProductName;
    [PropertyContext("Release")] string Release;
    [PropertyContext("SerialNumber")] string SerialNumber;
    [PropertyContext("StandaloneNetworkType")] string StandaloneNetworkType;
};

// AutoCAD 2000i
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\AutoCAD\\R15.1")
]

class Win32Reg_AutoCAD_2000i
{
    [Key] string KeyName;
    [PropertyContext("ProductName")] string ProductName;
    [PropertyContext("Release")] string Release;
    [PropertyContext("SerialNumber")] string SerialNumber;
    [PropertyContext("StandaloneNetworkType")] string StandaloneNetworkType;
};

// AutoCAD (including Mechanical) 2002
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\AutoCAD\\R15.2")
]

class Win32Reg_AutoCAD_2002
{
    [Key] string KeyName;
    [PropertyContext("ProductName")] string ProductName;
    [PropertyContext("Release")] string Release;
    [PropertyContext("SerialNumber")] string SerialNumber;
    [PropertyContext("StandaloneNetworkType")] string StandaloneNetworkType;
};

//AutoCAD (including Mechanical) 2004
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\AutoCAD\\R16.0")
]

class Win32Reg_AutoCAD_2004
{
    [Key] string KeyName;
    [PropertyContext("ProductName")] string ProductName;
    [PropertyContext("Release")] string Release;
    [PropertyContext("SerialNumber")] string SerialNumber;
    [PropertyContext("StandaloneNetworkType")] string StandaloneNetworkType;
};

//AutoCAD (including Electrical & Mechanical) 2005
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\AutoCAD\\R16.1")
]

class Win32Reg_AutoCAD_2005
{
    [Key] string KeyName;
    [PropertyContext("ProductName")] string ProductName;
    [PropertyContext("Release")] string Release;
    [PropertyContext("SerialNumber")] string SerialNumber;
    [PropertyContext("StandaloneNetworkType")] string StandaloneNetworkType;
};

//AutoCAD (including Electrical & Mechanical) 2006
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\AutoCAD\\R16.2")
]

class Win32Reg_AutoCAD_2006
{
    [Key] string KeyName;
    [PropertyContext("ProductName")] string ProductName;
    [PropertyContext("Release")] string Release;
    [PropertyContext("SerialNumber")] string SerialNumber;
    [PropertyContext("StandaloneNetworkType")] string StandaloneNetworkType;
};

//AutoCAD (including Electrical & Mechanical) 2007
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\AutoCAD\\R17.0")
]

class Win32Reg_AutoCAD_2007
{
    [Key] string KeyName;
    [PropertyContext("ProductName")] string ProductName;
    [PropertyContext("Release")] string Release;
    [PropertyContext("SerialNumber")] string SerialNumber;
    [PropertyContext("StandaloneNetworkType")] string StandaloneNetworkType;
};

//AutoCAD (including Electrical & Mechanical) 2008
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\AutoCAD\\R17.1")
]

class Win32Reg_AutoCAD_2008
{
    [Key] string KeyName;
    [PropertyContext("ProductName")] string ProductName;
    [PropertyContext("Release")] string Release;
    [PropertyContext("SerialNumber")] string SerialNumber;
    [PropertyContext("StandaloneNetworkType")] string StandaloneNetworkType;
};

//AutoCAD (including Electrical & Mechanical) 2009
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\AutoCAD\\R17.2")
]

class Win32Reg_AutoCAD_2009
{
    [Key] string KeyName;
    [PropertyContext("ProductName")] string ProductName;
    [PropertyContext("Release")] string Release;
    [PropertyContext("SerialNumber")] string SerialNumber;
    [PropertyContext("StandaloneNetworkType")] string StandaloneNetworkType;
};

//AutoCAD (including Electrical & Mechanical) 2010
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\AutoCAD\\R18.0")
]

class Win32Reg_AutoCAD_2010
{
    [Key] string KeyName;
    [PropertyContext("ProductName")] string ProductName;
    [PropertyContext("Release")] string Release;
    [PropertyContext("SerialNumber")] string SerialNumber;
    [PropertyContext("StandaloneNetworkType")] string StandaloneNetworkType;
};

//AutoCAD (including Electrical & Mechanical) 2011
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\AutoCAD\\R18.1")
]

class Win32Reg_AutoCAD_2011
{
    [Key] string KeyName;
    [PropertyContext("ProductName")] string ProductName;
    [PropertyContext("Release")] string Release;
    [PropertyContext("SerialNumber")] string SerialNumber;
    [PropertyContext("StandaloneNetworkType")] string StandaloneNetworkType;
};

//AutoCAD (including Electrical & Mechanical) 2012

[dynamic, provider("RegProv"), ClassContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\AutoCAD\\R18.2")]
Class Win32Reg_Autocad_2012
{
[key] string KeyName;
[PropertyContext("ProductName")] String ProductName;
[PropertyContext("Release")] String Release;
[PropertyContext("SerialNumber")] String SerialNumber;
[PropertyContext("StandaloneNetworkType")] String StandaloneNetworkType;
};

#pragma namespace ("\\\\.\\root\\cimv2")
//#pragma deleteclass("Win32Reg_Autocad_2012_64", NOFAIL)
[dynamic, provider("RegProv"), ClassContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\AutoCAD\\R18.2")]
Class Win32Reg_Autocad_2012_64
{
[key] string KeyName;
[PropertyContext("ProductName")] String ProductName;
[PropertyContext("Release")] String Release;
[PropertyContext("SerialNumber")] String SerialNumber;
[PropertyContext("StandaloneNetworkType")] String StandaloneNetworkType;
};

//***************************************
//* AutoCAD LT Starts Here
//***************************************

//AutoCAD LT 97
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\AutoCAD LT\\R4")
]

class Win32Reg_AutoCAD_LT_97
{
    [Key] string KeyName;
    [PropertyContext("ProductName")] string ProductName;
    [PropertyContext("Release")] string Release;
    [PropertyContext("SerialNumber")] string SerialNumber;
    [PropertyContext("StandaloneNetworkType")] string StandaloneNetworkType;
};

//AutoCAD LT 2000
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\AutoCAD LT\\R6")
]

class Win32Reg_AutoCAD_LT_2000
{
    [Key] string KeyName;
    [PropertyContext("ProductName")] string ProductName;
    [PropertyContext("Release")] string Release;
    [PropertyContext("SerialNumber")] string SerialNumber;
    [PropertyContext("StandaloneNetworkType")] string StandaloneNetworkType;
};

//AutoCAD LT 2000i
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\AutoCAD LT\\R7")
]

class Win32Reg_AutoCAD_LT_2000i
{
    [Key] string KeyName;
    [PropertyContext("ProductName")] string ProductName;
    [PropertyContext("Release")] string Release;
    [PropertyContext("SerialNumber")] string SerialNumber;
    [PropertyContext("StandaloneNetworkType")] string StandaloneNetworkType;
};

//AutoCAD LT 2002
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\AutoCAD LT\\R8")
]

class Win32Reg_AutoCAD_LT_2002
{
    [Key] string KeyName;
    [PropertyContext("ProductName")] string ProductName;
    [PropertyContext("Release")] string Release;
    [PropertyContext("SerialNumber")] string SerialNumber;
    [PropertyContext("StandaloneNetworkType")] string StandaloneNetworkType;
};

//AutoCAD LT 2004
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\AutoCAD LT\\R9")
]

class Win32Reg_AutoCAD_LT_2004
{
    [Key] string KeyName;
    [PropertyContext("ProductName")] string ProductName;
    [PropertyContext("Release")] string Release;
    [PropertyContext("SerialNumber")] string SerialNumber;
    [PropertyContext("StandaloneNetworkType")] string StandaloneNetworkType;
};

//AutoCAD LT 2005
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\AutoCAD LT\\R10")
]

class Win32Reg_AutoCAD_LT_2005
{
    [Key] string KeyName;
    [PropertyContext("ProductName")] string ProductName;
    [PropertyContext("Release")] string Release;
    [PropertyContext("SerialNumber")] string SerialNumber;
    [PropertyContext("StandaloneNetworkType")] string StandaloneNetworkType;
};

//AutoCAD LT 2006
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\AutoCAD LT\\R11")
]

class Win32Reg_AutoCAD_LT_2006
{
    [Key] string KeyName;
    [PropertyContext("ProductName")] string ProductName;
    [PropertyContext("Release")] string Release;
    [PropertyContext("SerialNumber")] string SerialNumber;
    [PropertyContext("StandaloneNetworkType")] string StandaloneNetworkType;
};

//AutoCAD LT 2007
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\AutoCAD LT\\R12")
]

class Win32Reg_AutoCAD_LT_2007
{
    [Key] string KeyName;
    [PropertyContext("ProductName")] string ProductName;
    [PropertyContext("Release")] string Release;
    [PropertyContext("SerialNumber")] string SerialNumber;
    [PropertyContext("StandaloneNetworkType")] string StandaloneNetworkType;
};

//AutoCAD LT 2008
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\AutoCAD LT\\R13")
]

class Win32Reg_AutoCAD_LT_2008
{
    [Key] string KeyName;
    [PropertyContext("ProductName")] string ProductName;
    [PropertyContext("Release")] string Release;
    [PropertyContext("SerialNumber")] string SerialNumber;
    [PropertyContext("StandaloneNetworkType")] string StandaloneNetworkType;
};

//AutoCAD LT 2009
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\AutoCAD LT\\R14")
]

class Win32Reg_AutoCAD_LT_2009
{
    [Key] string KeyName;
    [PropertyContext("ProductName")] string ProductName;
    [PropertyContext("Release")] string Release;
    [PropertyContext("SerialNumber")] string SerialNumber;
    [PropertyContext("StandaloneNetworkType")] string StandaloneNetworkType;
};

//AutoCAD LT 2010
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\AutoCAD LT\\R15")
]

class Win32Reg_AutoCAD_LT_2010
{
    [Key] string KeyName;
    [PropertyContext("ProductName")] string ProductName;
    [PropertyContext("Release")] string Release;
    [PropertyContext("SerialNumber")] string SerialNumber;
    [PropertyContext("StandaloneNetworkType")] string StandaloneNetworkType;
};

//AutoCAD LT 2011
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\AutoCAD LT\\R16")
]

class Win32Reg_AutoCAD_LT_2011
{
    [Key] string KeyName;
    [PropertyContext("ProductName")] string ProductName;
    [PropertyContext("Release")] string Release;
    [PropertyContext("SerialNumber")] string SerialNumber;
    [PropertyContext("StandaloneNetworkType")] string StandaloneNetworkType;
};

//***************************************
//* Inventor Starts Here
//***************************************

//All Inventor
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\Inventor")
]

class Win32Reg_Autodesk_Inventor
{
    [Key] string KeyName;
    [PropertyContext("ProductName")] string ProductName;
    [PropertyContext("Release")] string Release;
    [PropertyContext("SerialNumber")] string SerialNumber;
    [PropertyContext("StandaloneNetworkType")] string StandaloneNetworkType;
};

//***************************************
//* 3dsmax Starts Here
//***************************************

//3dsmax 9
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\3dsmax\\9.0")
]

class Win32Reg_3dsmax_9
{
    [Key] string KeyName;
    [PropertyContext("ProductName")] string ProductName;
    [PropertyContext("Release")] string Release;
    [PropertyContext("SerialNumber")] string SerialNumber;
    [PropertyContext("StandaloneNetworkType")] string StandaloneNetworkType;
};

//3dsmax 13
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\3dsmax\\13.0")
]

class Win32Reg_3dsmax_13
{
    [Key] string KeyName;
    [PropertyContext("ProductName")] string ProductName;
    [PropertyContext("Release")] string Release;
    [PropertyContext("SerialNumber")] string SerialNumber;
    [PropertyContext("StandaloneNetworkType")] string StandaloneNetworkType;
};

//3dsmax 14
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Autodesk\\3dsmax\\14.0")
]

class Win32Reg_3dsmax_14
{
    [Key] string KeyName;
    [PropertyContext("ProductName")] string ProductName;
    [PropertyContext("Release")] string Release;
    [PropertyContext("SerialNumber")] string SerialNumber;
    [PropertyContext("StandaloneNetworkType")] string StandaloneNetworkType;
};

//***************************************
//* Algor Starts Here
//***************************************
[ dynamic,
provider("RegProv"),
ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Algor, Inc.\\Algor Software\\Algor")
]

class Win32Reg_Algor
{
    [Key] string KeyName;
    [PropertyContext("Product Name")] string ProductName;
    [PropertyContext("Version")] string Version;
    [PropertyContext("Serial Number")] string SerialNumber;
    [PropertyContext("Installation Type")] string InstallationType;
};

//Total Auto Desk END******************************************************************************

Confimgr / SCCM Pro / Cons

ConfigMgr 2007 Limitations

 

 

What is DISTRIBUTION POINT (DP): A site system that has the role of storing package source files. Clients contact distribution points to obtain source files when they run advertised programs, advertised task sequences, or deployed software updates.
Types of Distribution Points:

Some distribution point types are not compatible with other distribution point types. For example, a branch distribution point cannot support Internet-based clients. The following table shows which types of distribution points can be combined and which are mutually exclusive.

1 Configuring a server share on a site system already configured to support Internet-based clients will cause content location requests to fail.

2 On branch distribution points, enable File Streaming to support streaming using server message blocks (SMB).

Bandwidth Control:
The following table summarizes the bandwidth controls as packages move through the Configuration Manager 2007 system.

Grouping Distribution Points : You can create groups of distribution points to facilitate the processes of copying packages to distribution points. Packages can then be targeted to a distribution point group rather than to individual distribution points. For example, you might create a group of distribution points as Region 1 DP’s and copy packages for only region1 Locations only to that distribution points.

Why to depend on Branch Distribution Point:

 

 

 

Internet based Clients Limitations

In native mode, clients communicate over HTTPS to the following site systems:

ü Management points

ü Default management point

ü Network load balanced management points

ü Proxy management point

ü Internet-based management point

ü Standard distribution points (not branch distribution points)

ü Software update points

ü State migration point

Features that Are Not Supported on the Internet

ü Branch distribution points (a branch distribution point cannot support Internet clients, and clients on the Internet cannot be configured as a branch distribution point)

ü Software distribution that is targeted to users (either directly or through Microsoft Windows security groups)

ü Client deployment over the Internet

ü Auto-site assignment

ü Network Access Protection (NAP)

ü Wake On LAN

ü Operating system deployment

ü Task sequences

ü Remote control

ü Out of band management in Configuration Manager 2007 SP1 and later

ü The client ping functionality used with the client status reporting feature in Configuration Manager 2007 R2

 

 

 

 

Asset Intelligence Reporting Limitations

Example Dependencies:

The accuracy of installed software title quantities and license information displayed in Asset Intelligence reports can vary from the actual amounts currently in use because of the complex dependencies involved in inventorying software license information for software titles in use in enterprise environments.

The following are example dependencies involved in inventorying installed software and license usage in the enterprise using Asset Intelligence that might affect the accuracy of Asset Intelligence reports:

Client hardware inventory dependencies:

Asset Intelligence installed software reports are based on data collected from SMS or Configuration Manager clients by extending hardware inventory to enable Asset Intelligence reporting. Because of this dependency on hardware inventory reporting, Asset Intelligence reports will reflect data only from SMS or Configuration Manager clients that successfully complete hardware inventory processes with the required Asset Intelligence WMI reporting classes enabled. In addition, because SMS or Configuration Manager clients perform hardware inventory processes on a schedule defined by the administrator, there might be a delay in data reporting that affects the accuracy of Asset Intelligence reports. For example, an inventoried, licensed software title might be uninstalled after the client completes a successful hardware inventory cycle, but the software title will still appear as installed in Asset Intelligence reports until the client’s next scheduled hardware inventory reporting cycle.

Software packaging dependencies

Because Asset Intelligence reports are based on installed software title data collected using standard SMS or Configuration Manager client hardware inventory processes, some software title data might not be properly collected. For example, software installations that do not conform to standard installation processes or software installations that have been modified prior to installation might result in inaccurate Asset Intelligence reporting results.

Server role dependencies

When utilizing CAL reporting, it is important to remember that these reports were designed to provide visibility into the usage of specific products in specific scenarios—for example, a server running a Windows Server operating system supporting a single server role. Licensed software title usage in different scenarios might produce inaccurate results—for example, the case of a server running a Windows Server operating system supporting multiple roles, such as Exchange mail server or SQL Server database server. When deciding to use Asset Intelligence to report license usage and information, keep in mind that it was designed only to provide visibility into license usage. For example, even if your license agreement allows you to use certain software in a lab or classroom environment without charge, Asset Intelligence will be able to detect only installed software in use and report it as such. In such a case, relying solely on Asset Intelligence might result in overpayment.

Location and usage

When deciding to use Asset Intelligence to report license usage and information, keep in mind that it was designed only to provide visibility into license usage. For example, even if your license agreement allows you to use certain software in a lab or classroom environment without charge, Asset Intelligence will be able to detect only installed software in use and report it as such. In such a case, relying solely on Asset Intelligence might result in overpayment.

Legal Limitations

The information displayed in Asset Intelligence reports are subject to many limitations and the information displayed in them does not constitute legal, accounting, or other professional advice. The information provided by Asset Intelligence reports is for informational purposes only and should not be used as the sole source of information for determining software license usage compliance.

The following are example limitations involved in inventorying installed software and license usage in the enterprise using Asset Intelligence that might affect the accuracy of

Asset Intelligence reports:

Microsoft license usage quantity limitations

The quantity of purchased Microsoft software licenses is based on information supplied by administrators and should be closely reviewed to ensure that the correct number of software licenses is provided.

The Microsoft software license quantity reported contains information only for Microsoft software licenses acquired through volume licensing programs and does not reflect information for software licenses acquired through retail, Original Equipment Manufacturer (OEM), or other software license sales channels.

Software licenses acquired in the last 45 days might not be included in the Microsoft software license quantities reported because of software reseller reporting requirements and schedules.

Software license transfers as a result of company mergers or acquisitions might not be reflected in Microsoft software license quantities.

Nonstandard terms and conditions in a Microsoft Volume Licensing (MVLS) agreement might affect the number of software licenses reported and, consequently, might require additional review by a Microsoft representative.

Installed software title quantity limitations

The accuracy of installed software title quantities in Asset Intelligence reports relies on fully functioning SMS or Configuration Manager clients successfully completing hardware inventory reporting cycles and installation on appropriate computers. Additionally, there might be a delay between installation or uninstallation of a licensed software title after a successful hardware inventory reporting cycle that will not be reflected in Asset Intelligence reports run before the client reports its next scheduled hardware inventory.

License reconciliation limitations

The reconciliation of installed software title quantities to the quantity of purchased software licenses is calculated by using a comparison of the license quantity specified by the administrator and the installed software title quantities collected from SMS or Configuration Manager client hardware inventories based on the schedule set by the administrator. This comparison does not represent a final license position conclusion by Microsoft. The actual license position depends on the specific software title license and usage rights granted by the license terms

 

 

 

Single Site Design can offer below:
MS Limitations: One DP can be supported maximum of 4000 clients

Pro:

ü Need only One standard DP

ü Need to Use Nomad

ü Package flow over the wan can be well controlled with Nomad

ü This was success in the current SMS hierarchy

ü No BDP’s Required

ü No PDP’s required

ü NO DP Groups Required as only one DP

Con:

ü Nomad is third party Software and need to pay extra cost to the licensing

ü Over administration need to done for every time when you create a package & advertise

ü We can use BDP’s, PDPs and DP Groups to specifically can target

ü You can’t push more than one Package at a time in a bandwidth control manner as nomad will treat this as separate package

ü Not tested for PXE request handling over the WAN with this model

ü You may not required Multicasting with this model for OSD

ü If we want to place DP in Leatherhead then you can’t control the Bandwidth on this DP until you have a Site (Primary / Secondary site) – However this is not in the immediate scope

ü You can’t use Streaming DP’S for APP-V in this model for enterprise level

 

 

 

Software Updates in Configuration Manager:

MS Limitations: One WSUS / SUP server can be supported about 25,000 clients

Pro:

ü All clients will gets scanned from One Active SUP server

Con:

ü Managing all 7000+ systems scanning from one system over the WAN need to take consideration

ü In slow WAN we may expect WUA scanning errors because of Network connectivity issues

ü Nomad Packages not tested for OSD

ü

 

 

 

Operating System Deployment in Configuration Manager:

 

MS Limitations: Up to 10 PXE service points per site, with a maximum of 75 PXE service points per primary site database

 

Pro:

ü We can successfully build OS in Camphill

ü Scope for only Camphill datacenter and well connected networks

ü Need to depend on full Zero Touch and Burn in DVD / Flash Disk and send to the Slow links (rest of the world location except Camphill)

 

Con:

ü Boot Images Source (About 150 MB to 180 MB) will be stored in Camphill server

ü Every time you build your server need to transfer (150 MB to 180 MB) Boot Image data over the WAN

ü In slow WAN we may not build the OS

ü 90% to 95% locations need to build with DVD / USB Flash

ü State Migration Points can enabled in the well connected networks and can do the easy windows Desktop OS migration to other desktop OS or Clean Desktop OS

 

 

Reporting & SRS in Configuration Manager

MS Limitations:- Report Viewer in Configuration Manager 2007 limits the result set returned by a report query to 10,000 rows. Report Viewer in Configuration Manager 2007 limits the number of rows returned to 1,000 rows when you click Values and the values list displays for a prompt.

Pro:

ü Enable on Central site can see enterprise level reports

Con:

ü Web Reports and SRS will exist on the same system or site

 

 

Remote Tools in Configuration Manager:

Pro:

ü Single SCCM Console

Con:

ü Multiple users can’t do a RDP

ü May need to allow then to install locally and use Remote Tools

ü May increase the Load on the WAN and user experience may decrease when use remote tools from WAN

ü This can remove Dame ware licensing cost

 

 

Wake On LAN in Configuration Manager:

Pro:

ü One WOL Server will be deployed entire the Network

ü All Magic Packets will be transmitted ( Unicast / subnet based broad cast)from Camphill to end computers

Con:

ü WAN Traffic may increase

 

Client & Server Communication:

Pro:

ü All configuration from one site one console

Con:

ü WAN Traffic may increase

ü Client Push or Client Deployment, Client Discovery information and all client communication will flow over the WAN regardless if clients are in slow Link

 

Internet based Clients:

MS Limitations:- see above

Pro:

ü SCCM Server need to configure as native mode and face external & internal clients

Con:

ü Not a good idea to expose the server without moving to DMZ

ü Below are the Scenarios that can be configure for SCCM in native mode to support Internet based clients as a best practice depend on the Scenario & requirement

· Scenario 1 with no SQL Server Replica

· Scenario 1 with SQL Server Replica

· Scenario 2 with Child Site

· Scenario 2 with Complete Hierarchy

· Scenario 3 with No SQL Server Replica

· Scenario 3 with SQL Server Replica

· Scenario 4 with Two Network Cards

· Scenario 4 with Internet Connections into the Intranet

· Scenario 4 with Intranet Connections into the Perimeter Network