Zero Touch Installation Deployment Feature Team Guide

Modify the CustomSettings.ini file to include the Role literal value in the Priority line (as illustrated in Listing 50).

Note Some parts of the following code snippet have been displayed in multiple lines only for better readability. These should be entered in a single line.

[Settings]
...
Priority=MacAddress, DefaultGateway, Role, Default
CustomKeysUserData=UDShare, UDDir, UDProfiles,
SLShare, OSInstall, Packages(*), Administrators(*),
PowerUsers(*), DriverPath(*), Role
...

Listing 50. Excerpt from the Customsettings.ini file that illustrates addition of the Role custom key

Create a value for the Role custom key in a section based on the computer’s MAC address as illustrated in Listing 51).

[00:03:FF:CB:4E:C2]
Role=Accounting

Listing 51. Excerpt from the Customsettings.ini file that illustrates computer-specific section that contains Role

This would assign the value “Accounting” to the Role custom key. That value would then be used (based on the inclusion of “Role” on the Priority list) to find a section in the CustomSettings.ini file named Accounting (as illustrated in Listing 51).

Create a section based on the value specified in the previous step, and populate the section with the packages to be deployed (as illustrated in Listing 52)

[Accounting]
Packages1=XXX00001-Program name 1
Packages2=XXX00002-Program name 2
Packages3=XXX00003-Program name 3

Listing 52. Excerpt from the Customsettings.ini file that illustrates the application packages installed for the Accounting role

The packages specified (XXX00001-Program name 1, XXX00002-Program name 2, and XXX00003-Program name 2) would be installed on the computer during the State Restore Phase of the deployment process.

Create a database table to query (as illustrated in Listing 53).

Note Some parts of the following code snippet have been displayed in multiple lines only for better readability. These should be entered in a single line.

use [BDDAdminDB]
go
 
if exists (select * from dbo.sysobjects where
id = object_id(N'[dbo].[RolePackages]') and
OBJECTPROPERTY(id, N'IsUserTable') = 1)
drop table [dbo].[RolePackages]
go
 
CREATE TABLE [dbo].[RolePackages] (
    [Role] [nvarchar] (50),
    [Packages] [nvarchar] (50)
)
go

Listing 53. Sample SQL Script to create a table used to associate packages with roles

Populate the table with data that associates the appropriate package with the appropriate roles (illustrated in Listing 54).

For example, you could insert a row for each package that needs to be installed (XXX00001-Program name 1, XXX00002-Program name 2, and XXX00003-Program name 2) for the Accounting role. Compare this to the information in Listing 52.

Note Some parts of the following code snippet have been displayed in multiple lines only for better readability. These should be entered in a single line.

use [BDDAdminDB]
go
 
insert into RolePackages (Role, Packages) 
values('Accounting', 'XXX00001-Program name 1')
go 
insert into RolePackages (Role, Packages) 
values('Accounting', 'XXX00002-Program name 2')
go
insert into RolePackages (Role, Packages) 
values('Accounting', 'XXX00003-Program name 3')
go

Listing 54. Sample data entered to associate packages with roles

Configure the CustomSettings.ini file to query this database table by specifying the name of a section (in the Priority list) that points to the database information (as illustrated in Listing 55).

Note Some parts of the following code snippet have been displayed in multiple lines only for better readability. These should be entered in a single line.

[Settings]
...
Priority=MacAddress, DefaultGateway, RoleQuery,
Default
CustomKeysUserData=UDShare, UDDir, UDProfiles,
SLShare, OSInstall, Packages(*), Administrators(*),
PowerUsers(*), DriverPath(*), Role
...

Listing 55. Excerpt from Customsettings.ini that illustrates modified Priority list

Create a RoleQuery section to specify the name of a database section (as illustrated in Listing 56).

[RoleQuery]
SQLDefault= DB_RoleQuery

Listing 56. Excerpt from Customsettings.ini that illustrates RoleQuery section with the name of a database section

Create the database section.

This section includes the database connection information and query details (as illustrated in Listing 57).

[DB_RoleQuery]
SQLServer=SERVER1
Database=BDDAdminDB
Table=RolePackages
Parameters=Role
SQLShare=Logs

Listing 57. Excerpt from Customsettings.ini that illustrates the database section

In the example in Listing 57, the BDDAdminDB database on the computer running SQL Server named SERVER1 will be queried. The database contains a table named RolePackages (created in step 1).

Modify the CustomSettings.ini file to include the DefaultGateway literal value in the Priority line (as illustrated in Listing 60).

[Settings]
...
Priority=MacAddress, DefaultGateway, Default
...

Listing 60. Excerpt from Customsettings.ini that illustrates the database section

The DefaultGateway value causes the ZTI rules engine to look for a section named [DefaultGateway]. The [DefaultGateway] section contains pointers to other sections that have the actual application package settings.

Create the [DefaultGateway] section (as illustrated in Listing 61).

[DefaultGateway]
192.168.0.1=HOUSTON
11.1.1.11=REDMOND
172.28.20.1=REDMOND
...

Listing 61. Excerpt from Customsettings.ini that illustrates [DefaultGateway] section

As illustrated in Listing 61, in the “REDMOND” section there are two different default gateway values (11.1.1.11 and 172.28.20.1). In the “HOUSTON” section there is only one default gateway value (192.168.0.1). You can use this method to deploy location-specific packages to REDMOND and HOUSTON.

Create a section for each default gateway specified in the [DefaultGateway] section (as illustrated in Listing 62).

[REDMOND]
Packages1=XXX00004-Program name 4
Packages2=XXX00005-Program name 5
 
[HOUSTON]
Packages1=XXX00006-Program name 6
Packages2=XXX00007-Program name 7
Packages3=XXX00008-Program name 8

Listing 62. Excerpt from Customsettings.ini that illustrates package selection based on the default gateway

Based on configuration settings in Listing 62, different packages (and a different number of packages) are installed on computers in REDMOND compared with HOUSTON.

Create a table in the BDDAdminDB database to relate location-specific packages with default gateways (as illustrated in Listing 63).

Note Some parts of the following code snippet have been displayed in multiple lines only for better readability. These should be entered in a single line.

use [BDDAdminDB]
go
 
if exists (select * from dbo.sysobjects where
id = object_id(N'[dbo].[LocationPackages]') and
OBJECTPROPERTY(id, N'IsUserTable') = 1)
drop table [dbo].[LocationPackages]
go
 
CREATE TABLE [dbo].[LocationPackages] (
    [DefaultGateway] [nvarchar] (50),
    [Packages] [nvarchar] (50)
)
go

Listing 63. Excerpt from Customsettings.ini that illustrates creating a table to use in database query

Populate the table with data that associates the appropriate package with the appropriate default gateway (as illustrated in Listing 64).

Note Some parts of the following code snippet have been displayed in multiple lines only for better readability. These should be entered in a single line.

use [BDDAdminDB]
go
 
insert into LocationPackages (DefaultGateway, Packages) 
values('11.1.1.11', 'XXX00004-Program name 4')
go 
insert into LocationPackages (DefaultGateway, Packages) 
values('11.1.1.11', 'XXX00005-Program name 5')
go
insert into LocationPackages (DefaultGateway, Packages) 
values('172.28.20.1', 'XXX00004-Program name 4')
go 
insert into LocationPackages (DefaultGateway, Packages) 
values('172.28.20.1', 'XXX00005-Program name 5')
go
insert into LocationPackages (DefaultGateway, Packages)
values('192.168.0.1', 'XXX00006-Program name 6')
go
insert into LocationPackages (DefaultGateway, Packages) 
values('192.168.0.1', 'XXX00007-Program name 7')
go
insert into LocationPackages (DefaultGateway, Packages)
values('192.168.0.1', 'XXX00008-Program name 8')
go

Listing 64. Sample data entered to associate packages with default gateways

Configure the CustomSettings.ini file to query this database table by specifying the name of a section (in the Priority list) that points to the database information (as illustrated in Listing 65).

Note Some parts of the following code snippet have been displayed in multiple lines only for better readability. These should be entered in a single line.

[Settings]
...
Priority=MacAddress, DefaultGateway, LocationQuery, 
Default
CustomKeysUserData=UDShare, UDDir, UDProfiles, 
SLShare, OSInstall, Packages(*), Administrators(*),
PowerUsers(*), DriverPath(*)
...

Listing 65. Excerpt from Customsettings.ini that illustrates LocationQuery section in the Priority list

Create a LocationQuery section to specify the name of a database section (as illustrated in Listing 66).

Note Some parts of the following code snippet have been displayed in multiple lines only for better readability. These should be entered in a single line.

This new LocationQuery section must then
specify the name of a database section.
[LocationQuery]
SQLDefault= DB_LocationQuery

Listing 66. Excerpt from Customsettings.ini that illustrates LocationQuery section with the name of a database section

Create the database section that contains the database connection and query details (as illustrated in Listing 67).

Note Some parts of the following code snippet have been displayed in multiple lines only for better readability. These should be entered in a single line.

Then that section specifies the database 
connection information and query details.
[DB_LocationQuery]
SQLServer=SERVER1
Database=BDDAdminDB
Table=LocationPackages
Parameters=DefaultGateway

Listing 67. Excerpt from Customsettings.ini that illustrates the database section

In the example in Listing 67, the BDDAdminDB database on the computer running the SQL Server named SERVER1 will be queried. The database contains a table named LocationPackages (created in step 1).

Create the tables in the BDDAdminDB database to relate location-specific packages with default gateways (as illustrated in Listing 69).

Note Some parts of the following code snippet have been displayed in multiple lines only for better readability. These should be entered in a single line.

use [BDDAdminDB]
go
 
if exists (select * from dbo.sysobjects where
id = object_id(N'[dbo].[SitePackages]') and 
OBJECTPROPERTY(id, N'IsUserTable') = 1)
drop table [dbo].[SitePackages]
go
if exists (select * from dbo.sysobjects 
where id = object_id(N'[dbo].[GatewayToSite]') and
OBJECTPROPERTY(id, N'IsUserTable') = 1)
drop table [dbo].[GatewayToSite]
go
if exists (select * from dbo.sysobjects where
id = object_id(N'[dbo].[LocationPackages]') and
OBJECTPROPERTY(id, N'IsView') = 1)
drop view [dbo].[LocationPackages]
go
 
CREATE TABLE [dbo].[SitePackages] (
    [Site] [nvarchar] (50),
    [Packages] [nvarchar] (50)
)
go

CREATE TABLE [dbo].[GatewayToSite] (
    [DefaultGateway] [nvarchar] (50),
    [Site] [nvarchar] (50)
)
go

CREATE VIEW [dbo].[LocationPackages] AS
SELECT a.Site, Packages, DefaultGateway FROM 
SitePackages a, GatewayToSite b
WHERE a.Site = b.Site
go

Listing 69. SQL query to create the tables and view

Populate the table with data that associates the appropriate package with the appropriate location (as illustrated in Listing 70).

Note Some parts of the following code snippet have been displayed in multiple lines only for better readability. These should be entered in a single line.

use [BDDAdminDB]
go

insert into GatewayToSite(DefaultGateway, Site)
values ('192.168.0.1', 'HOUSTON')
go
insert into GatewayToSite(DefaultGateway, Site)
values ('11.1.1.11', 'REDMOND')
go
insert into GatewayToSite(DefaultGateway, Site)
values ('172.28.20.1', 'REDMOND')
go

insert into SitePackages(Site, Packages) 
values('REDMOND', 'XXX00004-Program name 4')
go

insert into SitePackages(Site, Packages)
values('REDMOND', 'XXX00005-Program name 5')
go

insert into SitePackages(Site, Packages) 
values('HOUSTON', 'XXX00006-Program name 6')
go
insert into SitePackages(Site, Packages) 
values('HOUSTON', 'XXX00007-Program name 7')
go
insert into SitePackages(Site, Packages) 
values('HOUSTON', 'XXX00008-Program name 8')
go

Listing 70. Excerpt from Customsettings.ini that illustrates the database section

Configure the CustomSettings.ini file to query this database table by specifying the name of a section (in the Priority list) that points to the database information (as illustrated in Listing 71).

Note Some parts of the following code snippet have been displayed in multiple lines only for better readability. These should be entered in a single line.

[Settings]
...
Priority=MacAddress, DefaultGateway, LocationQuery,
Default
CustomKeysUserData=UDShare, UDDir, UDProfiles,
SLShare,OSInstall, Packages(*), Administrators(*),
PowerUsers(*), DriverPath(*)
...

Listing 71. Excerpt from Customsettings.ini that illustrates LocationQuery section in the Priority list

Create a LocationQuery section to specify the name of a database section (as illustrated in Listing 72).

Note Some parts of the following code snippet have been displayed in multiple lines only for better readability. These should be entered in a single line.

This new LocationQuery section must then
specify the name of a database section.
[LocationQuery]
SQLDefault= DB_LocationQuery

Listing 72. Excerpt from Customsettings.ini that illustrates LocationQuery Section with the name of a database section

Create the database section.

This section includes the database connection information and query details (as illustrated in Listing 73).

Note Some parts of the following code snippet have been displayed in multiple lines only for better readability. These should be entered in a single line.

Then that section specifies the database
connection information and query details.
[DB_LocationQuery]
SQLServer=SERVER1
Database=BDDAdminDB
Table=LocationPackages
Parameters=DefaultGateway

Listing 73. Excerpt from Customsettings.ini that illustrates the database section

In the example in Listing 73, the BDDAdminDB database on the computer running the SQL Server named SERVER1 will be queried. The database contains a table named LocationPackages (created in step 1).  

Modify the CustomSettings.ini file to include the Make literal value in the Priority list (as illustrated in Listing 75).

[Settings]
...
Priority=MacAddress, Make, Default
...

Listing 75. Excerpt from Customsettings.ini that illustrates adding Make to the Priority list

This will cause the ZTI rules engine to look for a section matching the current Make value (for example, Dell Computer Corporation).

Create a section for the computer manufacturer, and create subsection values for each model of (as illustrated in Listing 76).

[Dell Computer Corporation]
Subsection=Dell-%Model%

Listing 76. Excerpt from Customsettings.ini that illustrates adding a manufacturer section and subsections

Because these settings do not yet uniquely identify a particular make/model combination, further specification is required for each potential %Model% variable.

Create a section for each potential %Model% value, and include the packages to be installed in that section (as illustrated in Listing 77).

[Dell-Latitude D600]
Packages1=XXX00009-Program name 9
Packages2=XXX0000A-Program name 10

Listing 77. Excerpt from Customsettings.ini that illustrates the database section

In this example, the current Model value (for example, Latitude D600) will replace the %Model% string. Then a section matching the full Subsection value is located. In this example, two packages are installed on all Dell Latitude D600 models.

Note   You need to create similar sections for other make/model combinations.

Create the tables in the BDDAdminDB database to relate specific packages with make and model of computers (as illustrated in Listing 78).

Note Some parts of the following code snippet have been displayed in multiple lines only for better readability. These should be entered in a single line.

use [BDDAdminDB]
go

if exists (select * from dbo.sysobjects where 
id = object_id(N'[dbo].[MakeModelPackages]') and
OBJECTPROPERTY(id, N'IsUserTable') = 1)
drop table [dbo].[MakeModelPackages]
go

CREATE TABLE [dbo].[MakeModelPackages] (
    [Make] [nvarchar] (50),
    [Model] [nvarchar] (50),
    [Packages] [nvarchar] (50)
)
go

Listing 78. SQL query to create the tables

Populate the table with data that associates the appropriate package with the appropriate makes and models (as illustrated in Listing 79).

Note Some parts of the following code snippet have been displayed in multiple lines only for better readability. These should be entered in a single line.

Now you can populate that table with rows
for the sample Dell Latitude D600.
use [BDDAdminDB]
go

insert into MakeModelPackages (Make, Model, Packages)
values('Dell Computer Corporation', 'Latitude D600',
'XXX00009-Program name 9')
go 
insert into MakeModelPackages (Make, Model, Packages)
values('Dell Computer Corporation', 'Latitude D600',
'XXX0000A-Program name 10')
go

Listing 79. SQL query to populate the tables

Configure the CustomSettings.ini file to query this database table by specifying the name of a section (MakeModelQuery in the Priority list) that points to the database information (as illustrated in Listing 80).

Note Some parts of the following code snippet have been displayed in multiple lines only for better readability. These should be entered in a single line.

[Settings]
...
Priority=MacAddress, DefaultGateway, MakeModelQuery,
Default
CustomKeysUserData=UDShare, UDDir, UDProfiles, 
SLShare, OSInstall, Packages(*), Administrators(*),
PowerUsers(*), DriverPath(*)
...

Listing 80. Excerpt from Customsettings.ini that illustrates MakeModelQuery section in the Priority list

Create a MakeModelQuery section to specify the name of a database section (as illustrated in Listing 81).

[MakeModelQuery]
SQLDefault= DB_MakeModelQuery

Listing 81. Excerpt from Customsettings.ini that illustrates MakeModelQuery section with the name of a database section

Create a database section to specify the database information and query details (as illustrated in Listing 82).

[DB_MakeModelQuery]
SQLServer=SERVER1
Database=BDDAdminDB
Table=MakeModelPackages
Parameters=Make, Model
SQLShare=Logs

Listing 82. Excerpt from Customsettings.ini that illustrates the database section

In the example in Listing 82, the BDDAdminDB database on the computer running the SQL Server named SERVER1 will be queried. The database contains a table named MakeModelPackages (created in step 1).  

Modify the CustomSettings.ini file to include the MacAddress literal value in the Priority list (as illustrated in Listing 84).

[Settings]
...
Priority=MacAddress, DefaultGateway, Default
...

Listing 84. Excerpt from Customsettings.ini that illustrates adding MacAddress section in the Priority list

This causes the ZTI rules engine to look for a section based on the MAC address of the current computer.

Create a section for the MAC Address of each computer, and add the packages to the section (as illustrated in Listing 85).

[00:03:FF:CB:4E:C2]
Packages1=XXX0000B-Program name 11
Packages2=XXX0000C-Program name 12

Listing 85. Excerpt from Customsettings.ini that illustrates the MacAddress section for a specific computer

In this case, the two packages listed would be installed during the State Restore Phase on the computer with MAC address 00:03:FF:CB:4E:C2.

Create the table in the BDDAdminDB database to relate specific packages with the MAC address of the computers (as illustrated in Listing 86).

Note Some parts of the following code snippet have been displayed in multiple lines only for better readability. These should be entered in a single line.

use [BDDAdminDB]
go
 
if exists (select * from dbo.sysobjects where 
id = object_id(N'[dbo].[ComputerPackages]') and
OBJECTPROPERTY(id, N'IsUserTable') = 1)
drop table [dbo].[ComputerPackages]
go
 
CREATE TABLE [dbo].[ComputerPackages] (
    [MacAddress] [nvarchar] (50),
    [Packages] [nvarchar] (50)
)
go

Listing 86. SQL query to create the table

Populate the table with data that associates the appropriate package with the appropriate MAC addresses (as illustrated in Listing 87).

Note Some parts of the following code snippet have been displayed in multiple lines only for better readability. These should be entered in a single line.

use [BDDAdminDB]
go

insert into ComputerPackages (MacAddress, Packages)
values('00:03:FF:CB:4E:C2', 'XXX0000B-Program name 11')
go 
insert into ComputerPackages (MacAddress, Packages)
values('00:03:FF:CB:4E:C2', 'XXX0000C-Program name 12')
go

Listing 87. SQL query to populate the table

Configure the CustomSettings.ini file to query this database table by specifying the name of a section (ComputerQuery in the Priority list) that points to the database information (as illustrated in Listing 88).

Note Some parts of the following code snippet have been displayed in multiple lines only for better readability. These should be entered in a single line.

[Settings]
...
Priority=MacAddress, DefaultGateway, ComputerQuery,
Default
...

Listing 88. Excerpt from Customsettings.ini that illustrates ComputerQuery section in the Priority list

Create a ComputerQuery section to specify the name of a database section (as illustrated in Listing 89).

[ComputerQuery]
SQLDefault= DB_ComputerQuery

Listing 89. Excerpt from Customsettings.ini that illustrates ComputerQuery section with the name of a database section

Create a database section to specify the database information (as illustrated in Listing 90).

[DB_ComputerQuery]
SQLServer=SERVER1
Database=BDDAdminDB
Table=ComputerPackages
Parameters=MacAddress
SQLShare=Logs

Listing 90. Excerpt from Customsettings.ini that illustrates the database section

In the example in Listing 90, the BDDAdminDB database on the computer running the SQL Server named SERVER1 will be queried. The database contains a table named ComputerPackages (created in step 1).  

Create the table in the BDDAdminDB database to relate specific packages with applications listed in Add/Remove Programs (as illustrated in Listing 92).

Note Some parts of the following code snippet have been displayed in multiple lines only for better readability. These should be entered in a single line.

use [BDDAdminDB]
go
 
if exists (select * from dbo.sysobjects where
id = object_id(N'[dbo].[PackageMapping]') and
OBJECTPROPERTY(id, N'IsUserTable') = 1)
drop table [dbo].[PackageMapping]
go
 
CREATE TABLE [dbo].[PackageMapping] (
    [ARPName] [nvarchar] (50),
    [Packages] [nvarchar] (50)
)
go

Listing 92. SQL query to create the tables

Populate the table with data that associates the appropriate package with the application listed in Add/Remove Programs (as illustrated in Listing 93).

Note Some parts of the following code snippet have been displayed in multiple lines only for better readability. These should be entered in a single line.

use [BDDAdminDB]
go
INSERT INTO [PackageMapping] (ARPName, Packages)
VALUES('Office8.0', 'XXX0000F-Install 
Office 2003 Professional')
go

Listing 93. SQL query to populate the table

In Listing 93, the inserted row relates any computer that has the “Office8.0” entry in Add/Remove Programs with the SMS Office 2003 Professional package. This means that Office 2003 Professional will be installed on any computer currently running Office 97 (Office 8.0). Similar entries can be added for any other packages; any Add/Remove Programs for which there is no entry will be ignored. (No package will be installed.)

Create a stored procedure to simplify joining the information in the new table with the SMS inventory data (as illustrated in Listing 94).

Note Some parts of the following code snippet have been displayed in multiple lines only for better readability. These should be entered in a single line.

use [BDDAdminDB]
go

if exists (select * from dbo.sysobjects where
id = object_id(N'[dbo].[RetrievePackages]') and
OBJECTPROPERTY(id, N'IsProcedure') = 1)
drop procedure [dbo].[RetrievePackages]
go

CREATE  PROCEDURE [dbo].[RetrievePackages]
@MacAddress CHAR(17)
AS

SET NOCOUNT ON

/* Select and return all the appropriate records
based on current inventory */
SELECT * FROM PackageMapping
WHERE ARPName IN
(
  SELECT ProdID0 FROM 
SMS_SMS.dbo.v_GS_ADD_REMOVE_PROGRAMS a,
SMS_SMS.dbo.v_GS_NETWORK_ADAPTER n
  WHERE a.ResourceID = n.ResourceID AND
  MACAddress0 = @MacAddress
)
go

Listing 94. SQL query to create a stored procedure to simplify joining the information with SMS inventory data

The stored procedure in Listing 94 assumes the SMS central primary site database resides on the same computer running SQL Server as the BDDAdminDB database. If the SMS central primary site database resides on a different computer, the appropriate modifications need to be made to the stored procedure. In addition, the name of the SMS database (SMS_SMS in Listing 94) needs to be updated. You may also need to grant additional accounts read access to the v_GS_ADD_REMOVE_PROGRAMS view in the SMS database.

Configure the CustomSettings.ini file to query this database table by specifying the name of a section (DynamicPackages in the Priority list) that points to the database information (as illustrated in Listing 95).

Note Some parts of the following code snippet have been displayed in multiple lines only for better readability. These should be entered in a single line.

[Settings]
...
Priority=MacAddress, DefaultGateway, DynamicPackages,
Default
...

Listing 95. Excerpt from Customsettings.ini that illustrates DynamicPackages section in the Priority list

Create a DynamicPackages section to specify the name of a database section (as illustrated in Listing 96).

[DynamicPackages]
SQLDefault= DB_DynamicPackages

Listing 96. Excerpt from Customsettings.ini that illustrates DynamicPackages section with the name of a database section

Create a database section to specify the database information and query details (as illustrated in Listing 97).

 [DB_DynamicPackages]
SQLServer=SERVER1
Database=BDDAdminDB
StoredProcedure=RetrievePackages
Parameters=MacAddress
SQLShare=Logs

Listing 97. Excerpt from Customsettings.ini that illustrates the database section

In the example in Listing 97, the BDDAdminDB database on the computer running the SQL Server named SERVER1 will be queried. The database contains a stored procedure named RetrievePackages (created in step 3).  

Users request applications to be installed on their computers.

Approval is obtained for each application requested.

A RunScript building block or equivalent business rule can be used to store a record on the ComputerPackages table.

You can retrieve the MAC address of the computer from the SMS database, as the provisioning request would only know the name of the computer.

The SMS inventory is used to insert records into the ComputerPackages table based on the current SMS inventory and contents of the PackageMapping table. This would be a one-time process.

The ZTP services described in Scenario 6 can be used to allow the user to make the needed modifications (subject to the same approvals described).