Security keys

Security keys

Security keys are the permissions that control access to functionality within the application, and are set to individual user groups and users.

Security keys are set up from Administration > Setup > Security > User group permissions on the Permissions tab.
Within a security profile, you can assign permissions that define access to Menu items, Form controls, Tables and Fields.
There are five available access levels:

• No access - Completely restricts access to that item and any sub-items it controls. The Open command is disabled. Also, the node is not displayed in the Application Object Tree (AOT).
• View access - Members of the user group are allowed to view the item, but not use it. The Save, Compile, Lock and Unlock commands are disabled.
• Edit access - Members of the user group are allowed to view and use the item. The New, Duplicate and Rename commands are disabled.
• Create access - Members of the user group are allowed to view and use, as well as add new items. The Delete command is disabled.
• Full control - Members of the user group have full access and consequently no commands are disabled. Additionally, members can provide additional rights in special cases.

Security access for each user must be decided before they first log on. Access depends on which user groups the user is a member of, and which company or domain the user is a member of. Access to functionality of each security key can depend on its parent, so the calculation must be done hierarchically.
To configure security keys, the administrator first selects a User Group and a corresponding Domain (it is possible to select all domains at once). The security tree is then built, and the administrator is able to view the tree and make the necessary changes.

Note
When a security key property is changed for any AOT object, the client must be restarted for the changes to become visible.

For information about how to set security keys and for information about best practices, see Set up security keys¹.

Security key logic and organization

---

Security keys are used to restrict user group access in Microsoft Dynamics AX. Security keys have two main properties:

• Configuration Keys – The Configuration Key system allows an administrator to set the availability of functionality for the entire system. These modifications are to subsets of a module's functionality that are not currently necessary to have enabled within the system. From a security perspective, the removal of unused functionality reduces the surface that is open to attack. For more information, see Enable and disable configuration keys².
• Parent (only one parent can be specified) – Parent/child relationships control whether a key can be disabled. If you assign permission to a parent-node key (for example, if you select Absence approver and then select Full control) all child nodes inherit the same permission. If you do not want all child nodes to inherit the same permission, you can change permissions on individual child nodes.

The following graphic shows the path that is taken to validate security access.

Note
If you have set up domains within Microsoft Dynamics AX, security is applied to the individual domains. Otherwise, security is set up for all companies.

Each parent security key represents a broad umbrella of functionality within Microsoft Dynamics AX, and the underlying child security keys are divided into eight categories: Daily, Setup, Journals, Inquiries, Reports, Periodic, Miscellaneous and Tables. Each module in Microsoft Dynamics AX is broken down within these categories. The Security keys are laid out similar to the structure in the User Interface. Opening the main menu side-by-side with the security keys makes it easy to see how the categories relate to menu items.

• Daily — Contains the most accessed forms in the menu
• Setup — Corresponds with the Setup folder in the menu
• Journals — Corresponds with the Journals folder in the menu
• Inquiries — Corresponds with the Inquiries folder in the menu
• Reports — Corresponds with the Reports folder in the menu
• Periodic — Corresponds with the Periodic folder in the menu
• Miscellaneous — Controls access to all menu items used in the module that are not accessed from the menu. This is typically menu items accessed through buttons on forms. You do not have to change access in this category directly if you click Cascade.
  

  Note
  When you give access to a form, clicking Cascade updates all items with the same access related to that form.

• Tables — Lists all the tables used in that module. Clicking Cascade ensures that all tables are accessible for needed forms and reports.

See Best Practices for Configuration and Security Keys³ for more information about Security key and Menu relationships.

For each module, a set of nine security keys exists. They all have the same naming, and the prefixes denote the module. For the Accounts Receivable module, the security keys are:

• Cust
• CustDaily
• CustSetup
• CustJournals
• CustInquiries
• CustReports
• CustPeriodic
• CustMisc
• CustTables

Each menu item is present beneath one (and only one) security key. The access to the menu item ranges from No access to Full control.

See Also

---

Set up security keys¹

Microsoft Dynamics AX configuration hierarchy⁴

Set up application security⁵

Links Table

¹http://msdn.microsoft.com/en-us/library/aa548687(v=ax.10).aspx

²http://msdn.microsoft.com/en-us/library/aa496468(v=ax.10).aspx

³http://msdn.microsoft.com/en-us/library/aa590456(v=ax.10).aspx

⁴http://msdn.microsoft.com/en-us/library/aa497062(v=ax.10).aspx

⁵http://msdn.microsoft.com/en-us/library/aa834392(v=ax.10).aspx

Community Content

© 2012 Microsoft. All rights reserved.

Sharing Business Information the Easy Way: Microsoft Dynamics AX 2012 Enterprise Portal - Inside Microsoft Dynamics AX - Site Home - MSDN Blogs

Sharing Business Information the Easy Way: Microsoft Dynamics AX 2012 Enterprise Portal - Inside Microsoft Dynamics AX - Site Home - MSDN Blogs:

Too often, organizations make business data and business applications available only to back-office workers. By limiting access in this way, they miss out on the benefits of providing everyone in the company with real-time information and the ability to make informed decisions quickly enough to keep up with the competitive, ever-changing business world.

On the face of it, sharing business information should be straightforward, but in reality, there are some challenges, including business applications that were not designed with sharing in mind and a variety of user interfaces to choose from. Enterprise Portal in Microsoft Dynamics AX 2012 addresses these challenges by providing a web-based interface to the enterprise resource planning (ERP) system, and prebuilt support for a number of common business processes.

In Microsoft Dynamics AX 2012, we’ve made some major improvements to Enterprise Portal to:

• Make it easier for people to complete tasks in fewer steps and in less time.
• Help businesses respond quickly to changing needs and opportunities.
• Lower the costs associated with installing and maintaining web applications and portal sites.

Easy to Use

We heard from customers and partners that the user interface has a strong influence on the adoption and, therefore, on the long-term return-on-investment (ROI) of an ERP solution. In this release, the Enterprise Portal user interface has gone through a major revision, making it much easier for business users to navigate. We modeled the user experience on the familiar Microsoft Office and Windows interfaces, so the user experience should be more intuitive and consistent across all the Microsoft products that people use every day. In addition, we reduced the number of steps required to complete common tasks and made information and actions more easily discoverable, which should reduce the time people spend completing routine tasks.

Flexible and Extensible

Our customers also tell us that they need to constantly update business processes in response to changing market conditions or to improve operational efficiencies. The latest release of Enterprise Portal supports this need for agility by simplifying the development cycle and providing a set of first-class development tools.

Most notably, we’ve adopted a model that lets you share code between Microsoft Dynamics AX and the web-based portal environment. This approach can significantly reduce the development effort required to implement customizations in the parallel environments, while also ensuring easier maintenance and consistency across the two platforms.

In addition, we’ve upgraded the development tools for the Enterprise Portal in both MorphX and Microsoft Visual Studio so that developers can work in X++, Microsoft ASP.NET, or any other .NET language. We’ve also made it possible for multiple developers to work on the same code on the same server, so that teams can build applications more quickly

Simple to Install and Maintain

Deploying and maintaining applications on a large website can be a daunting task for the administrator. The Enterprise Portal team has invested heavily, building several utilities that simplify the installation and configuration process, as well as the day-to-day maintenance of your portal site.

During install, we’ve included a utility that developers can run before deployment or during setup to verify the readiness of the machines and detect prerequisites, eliminating many of the time-consuming, tedious tasks associated with implementing Enterprise Portal, especially across complex topologies.

After you set up Enterprise Portal, you can easily deploy subsequent changes by using a command-line utility that you can execute from a remote machine. This simplifies the management of multiple servers from a single place. The command-line utility also provides options to granularly deploy updates to a single Enterprise Portal site or to bulk update all websites with all changes.

Changes to the security model in Microsoft Dynamics AX also make it easier to manage large numbers of external users. In this release, we’ve added support for claims-based authentication so that customers can choose among standard Windows authentication methods, a separate database of user names and passwords, or connecting to an external identity management system, such as a Windows Live ID.

In this interview, Anees Ansari, Program Manager for the Enterprise Portal, provides a good overview (including a demo) on the advances made in the Enterprise Portal technology in MS Dynamics AX2012

Microsoft Dynamics AX 2012 BI

Microsoft Dynamics AX 2012 BI and Reporting includes more
than 800 Microsoft SQL Server® Reporting Services reports, 11
SQL Server Analytics Server data cubes, and enhancements to
the framework.
Microsoft SQL Server Reporting Services
• Microsoft Dynamics AX production reports combine the power
of SQL Server Reporting Services with the simplicity and flexibility
of Microsoft Dynamics AX. Along with more than 800 built-in
reports, Microsoft Dynamics AX 2012 will provide a wizard-based
migration tool for existing X++ reports and integrated, role-based
security options.
• Help meet exacting reporting requirements and reduce IT workload,
with auto-generation of SQL Server Reporting Services reports,
and create basic reports using the Microsoft Visual Studio® 2010
Charting Control.
• Support global operations: develop a report in one language, and
let the reporting framework produce reports in multiple languages.
Microsoft SQL Server Analysis Server
• Instantly identify and take action on business process issues
using new cubes for workflow and environmental sustainability.
Track history and current status, and generate performance
analysis reports.
• Easily implement, configure, and customize prebuilt data cubes
using a wizard-driven UI, which helps you deploy prebuilt business
intelligence solutions when you set up Microsoft Dynamics AX 2012.

Create a VHD File

Steps to create a VHD File:
1- Install Windows 7 on your machine (Host OS) .
2- Boot your machine with Windows Server 2008 R2 from a DVD or USB.
3- At the welcome Screen, Press Shift + F10 to enter the command prompt.
4- Type diskpart and press enter.
5- Creatae a VHD File => create vdisk file="c:\WinServer2008R2.vhd" maximum=25000 type=fixed and press enter.
    **type = fixed or expandable (For development enviroment Fixed is better because the I/O will be much faster than expandable)
    **maximum = Size of VHD file in MB
6- select the VHD File => select vdisk  file="c:\WinServer2008R2.vhd" and press enter.
7- Attach VHD => attach vdisk and press enter.
8- Exit diskpart => exit and press enter.
9- Close the command prompt and continue in installation.
10- Choose your new VHD (will appear as a partition) to install your Windows Server 2008 R2.

I am running SharePoint 2010 smoothly now :)

To Manage your boot menu in windows 7.
Use the command bcdedit.exe, from command prompt, but you need to run it as administrator.

Renameserver: Stsadm operation (Office SharePoint Server )

Description

Changes the name of the specified server in the configuration database.
This operation is used before or after a server is renamed in the domain to avoid having to rebuild the server or farm.

Syntax

stsadm -o renameserver
-oldservername
-newservername

Parameters

Parameter name and short form	Value	Required?	Description
oldservername	A valid server name, such as "OldServer"	Yes	The old name of the server listed on the Servers in Farm page of the SharePoint Central Administration Web site.
newservername	A valid server name such as "NewServer"	Yes	The new name of the server listed on the Servers in Farm page of the SharePoint Central Administration Web site.

Remarks

The renameserver operation cannot be used to rename query and index servers.
If the renameserver operation is used to make a name change on a computer that runs SQL Server and hosts the configuration database, then the renameserver operation must be run on every front-end Web server and application server in the farm. However, if the renameserver operation is used to make a name change on a computer that runs SQL Server and hosts databases other than the configuration database, you only need to run the renameserver operation on one server in the farm.

Main link http://technet.microsoft.com/en-us/library/cc263117(office.12).aspx