Logo
programming4us
programming4us
programming4us
programming4us
Home
programming4us
XP
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server
programming4us
Windows Phone
 
Windows Server

Microsoft Systems Management Server 2003 : Creating Packages for Distribution (part 2) - Creating a Package from Scratch - Defining Access Accounts

- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019
4/15/2013 6:17:31 PM
Defining Access Accounts

By default, when SMS creates the SMSPKGx$ share, it grants Read access to the local Users group and Full Control to the Administrators group. The default Users and Administrators entries map to the local Users and Administrators groups for Windows distribution points. These accounts are known as generic package access accounts.

Since the default share is a hidden share, the only way a client should know that a package is available to it is through the package distribution process. In other words, the client agent will see an advertisement for that package that targets a collection the client is a member of. Bear in mind that users will be users, and it’s possible that they will find the hidden share, navigate to a package folder, and execute any programs they find there. This could also happen if you create your own shares.

There are a couple of ways to deal with this little breach of security. One would be for you to evaluate the share (or NTFS) security for the SMS shares or for the package folders within the share. This is a time-consuming and potentially destructive process if you happen to lock out SMS from accessing the share. The other solution is to define access accounts for the package through the SMS Administrator Console. When you define an access account, you also define the level of access or permission for the specified user or group. This is much like creating ACLs in Windows.

To define an access account, follow these steps:

1.
Navigate to the Packages folder, find your package entry, and expand it.

2.
Right-click Access Accounts, choose New from the context menu, and then choose the type of access account you want to create.

3.
The two types of access accounts are listed here:

  • Windows User Access Account —Defines a Windows user or group account and the level of permission to allow

  • Generic Access Account —Defines additional or replacement user, guest, or administrator accounts and the level of permission to allow that maps to an operating system–specific account

Select the appropriate option to display the Access Account Properties dialog box, shown in Figure 8.

Figure 8. The Access Account Properties dialog box.


4.
Click Set to specify the account information as follows:

  • For a Windows user account, the Windows User Account dialog box will appear, as shown in Figure 9. Enter the user or group account in \\Domain\user format, and select User or Group.

    Figure 9. The Windows User Account dialog box.

  • For a Generic account, the Generic Account dialog box will appear, as shown in Figure 10. Select the account type.

    Figure 10. The Generic Account dialog box.

5.
Click OK to return to the Access Account Properties dialog box. Select the appropriate level of permissions from the Permissions drop-down list, as shown in Figure 11. For most applications, Read permission will be sufficient. However, if the program requires any kind of writing back to the source directory, you’ll need to assign at least Change permission.

Figure 11. The Permissions list of the Access Account Properties dialog box.


6.
Click OK to create the account.
Other -----------------
- Microsoft Systems Management Server 2003 : Running Software Metering Reports
- Microsoft Dynamics GP 2010 : Improving performance by adjusting AutoComplete settings, Cleaning up Accounts Receivable with Paid Transaction Removal
- Microsoft Dynamics GP 2010 : Maintaining Dynamics GP - Preventing entry of wrong dates by Closing Periods
- Windows Server 2008 R2 : Creating and Administering Hyper-V Virtual Machines (part 2) - Installing the guest operating system
- Windows Server 2008 R2 : Creating and Administering Hyper-V Virtual Machines (part 1) - Virtual machine disk types
- Backup and Restore of Microsoft Lync Server 2010 : Backup Processes (part 2) - Backing Up the Central Management Store, Backing Up Lync Server Servers
- Backup and Restore of Microsoft Lync Server 2010 : Backup Processes (part 1) - Backing Up Lync Server Databases
- SQL server 2008 R2 : Creating and Managing Stored Procedures - Using Input Parameters
- SQL server 2008 R2 : Creating and Managing Stored Procedures - Modifying Stored Procedures
- Microsoft Dynamics Ax 2009 : RunBase Framework Extension (part 4) - Adding a Query
 
 
Top 10
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
 
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server