Quick Guide - Out of Band Console Error - Current User Can't View This Page



A number of issues have arisen with a common symptom.  When clicking on a provisioning node for Out of Band Management Solution, A sequence of errors appear at the bottom of the page.  The causes vary, so it is important to understand the extend of the actual issue so that the proper resolution can be used to resolve the issue.  These errors include:


  • Current User Can't View This Page

  • Current User Can't Change Settings on This Page


You've just installed or Upgraded Altiris Out of Band Management Solution, including the Intel SCS component, and the Provisioning console pages are throwing the following error:


  • Error connecting to the Intel® AMT Setup and Configuration Server.  Verify that Intel® AMT Setup and Configuration Server security settings are configured and AMTConfig service is running.  See documentation for details on troubleshooting the Intel® Setup and Configuration Server installation.

  • The connection to the database has been reset

  • Current User Can't View This Page

  • Current User Can't Change Settings on This Page


The console page that loads will be completely grayed out and no functions can be used.  See this screenshot for an example of this error:




Issue Causes

Thus far we have three known causes to this issue.  The problems are details in this section, with the resolutions corresponding by number under the Issue Resolutions section.  Potentially the following basic environmental  items may contribute to the cause of this issue:


  1. A silent install conducted by the Out of Band Management installation is unable to authenticate and fails.

  2. Microsoft SQL Server 2000 is a common thread among the issues I've worked on.

  3. Having SQL Server off box from the Altiris Notification Server is another factor that appears to be common.


NOTE: These items are theory only at this point, but may help in identifying this issue.



*I. SQL Security Model</stroIntel SCS database only supports a mixed-mode security model in SQL.  By default the automatic scripted install for Intel SCS conducted silently when installing Out of Band Management will capture any warnings or errors, and will allow an install even if SQL is only set to Windows Only mode.  Both SQL 2000 and 2005 have the ability run SQL in one or the other modes.</p>


The two security models operate as follows:


  1. Windows Only Authentication - This mode requires all security users to be a member of the local Windows computer security groups, or part of a Domain with rights to the local SQL Server.

  2. Windows and SQL Authentication (Mixed Mode) - This mode works the same way with Windows or Domain users as the Windows Only mode, but adds the ability to define SQL specific users.  This includes the common SA account that defaults as a Database Enterprise Administrator.


The way Intel SCS is architected, the mode must be set to Windows and SQL Authentication (Mixed Mode).


II. File Access and Permissions

During the install we've seen a number of file access and permission issues.  These stem from either having a file locked during the installation, or having previous failed install steps setting incorrect permissions on the Intel SCS registry keys.  Often it is difficult to tell where the file or registry permission problem lies, but the error thrown in a popup during the Intel SCS install is the same:



LaunchAppAndWait failed!

Failed to add login user

Error code: 104



To discover where the actual permission issue lies, use the following steps in conjunction with the attached .bat file named Add_LoginToDB.zip :


  1. Shut down all SQL tools such as SQL Enterprise Manager or SQL Management Studio

  2. Stop the AMTConfig Service from the mmc Services console.

  3. In mmc Services, stop the IIS admin service.

  4. Close all Altiris Consoles.

  5. Log onto the Notification Server as the account that was set when installing Intel SCS (if you used a silent install this will be the NS Application Identity).

  6. Edit the downloaded script as follows:

    1. Change the first line to @echo on - This will allow us to watch the complete script including authentication or security errors.

    2. At the line set USER=TEST\ADMINISTRATOR - change the user context to the admin user you used to install SCS (you should be logged in as this user).

    3. Ensure the line set SCRIPTS="C:\Program Files\Intel\AMTConfServer\DB" - is set to the correct install path.

    4. Change the line set DB_SERVER=localhost\SQLMSDE - to the name of the SQL instance including the server name.  If running the default single instance, it will usually be simply the server name of the SQL Server.  If it is a specific instance, use the server name \ name of the instance.

  7. Save the script and place it at this location: C:\Program Files\Intel\AMTConfServer\DB.

  8. Now open a command prompt and browse to the above location.

  9. Execute the script.  The text will let you know if it was successful or if a problem occurred.

  10. If no error occurred it's possible the above procedure resolved the issue.  Note that at the beginning of the procedure we closed down potential file-lock applications or interfaces, which may have resolved the issue.

III. SCS Upgrade from version 1.3 to 3.0

This issue stems from an incompatibility between the two versions.  Opposite to standard assumptions, the 1.3 version of SCS was released after version 3.0 from Intel.  Version 1.3 was a hot fix to resolve an issue with the AMTConfig service crashing.  Due to this problem it became expedient to find a way to upgrade those on 1.3 to 3.0 since Out of Band 6.2 required Intel SCS 3.0.



See the resolution section for steps on how to resolve this issue.


Issue Resolutions

The following resolutions correspond in number to the Issue Causes listed in the preceding section.  The causes area exclusively unique, meaning only the resolution listed for the specific cause will resolve the issue for that instance.


I. SQL Security Model Resolution

The following procedures will change SQL to act in mixed mode.



In Microsoft SQL Server 2005, follow these steps to change the security mode:


  1. Open Microsoft SQL Server Management Studio.

  2. Right-click on the instance (if installed locally with a default instance it will be the name of the server) and choose Properties.

  3. Under the Select a Page pane, click on Security.

  4. Under Server authentication select SQL Server and Windows Authentication mode.



  1. This may require you to set a password on the SA account.

  2. Click OK.  The changes should be immediate.


In Microsoft SQL Server 2000, follow these steps to change the security mode:


  1. Open SQL Enterprise Manager.

  2. Right-click on the instance (if installed locally with a default instance it will be named ‘local') and choose Properties.

  3. Click on the ‘Security' tab.

  4. Under the ‘Authentication' heading change the radial option from ‘Windows Only' to ‘SQL Server and Windows'.

  5. Click OK to apply the changes.

II. File Access and Permissions Resolution

The initial steps provided in the II. Section under the Issue Causes may address the issue if it is a file-lock issue.  If so, great!  If not, an error should have been thrown when the script ran.  This should allow you to focus on where the permission problem is occurring.



Example: A recent issue stemmed from a botched install where the following registry key was created with incorrect permissions:  HKLM | Software | Intel | AMTConfServer.  This registry key only had a single user with rights.  Even local Administrators could not delete or modify the key.  The resolution steps are as follows:


  1. Uninstall the Intel SCS Component.

  2. Log in as the user shown to have permissions to this key.

  3. Delete the key from AMTConfServer on down.

  4. Log back in as the account you wish SCS to run under.

  5. Shut down all SQL tools such as SQL Enterprise Manager or SQL Management Studio

  6. Stop the AMTConfig Service from the mmc Services console.

  7. In mmc Services, stop the IIS admin service.

  8. Close all Altiris Consoles.

  9. Run the Intel SCS Install again.

III. SCS Upgrade from Version 1.3 to 3.0 Resolution

If you've already tried to upgrade, follow these instructions:



The following items should be covered when referencing the steps below:


  • SQL Database console: Make sure all SQL consoles are closed when you run the script.

  • AMTConfig: Stop this service by the Services manager.

  • IIS service: Stop the IIS process.

  • Close all Altiris Consoles.




  1. Delete "%Program Files%\intel\AMTConfServer\DB" folder.

  2. Copy all the files from the DB1.zip attached file to %sysdrive%\program files\intel\amtconfServer\Db.

  3. Add the next value to the registry: String: "SkipSCSCheck" value: "yes".

  4. Change in the SQL DB IntelAMT &gt; (Table) dbo.csti_configuration &gt; (Field) db_version to 1.1.

  5. Edit the file Upgrade1_3to3_0wLOGIN.bat located at the Db location extracted above to the right data (SQL server name and Domain\user name).

  6. Restart stopped services. You should now be able to connect to the database.


If you have not yet upgraded, these steps can be followed to upgrade:


  1. Delete "%Program Files%\intel\AMTConfServer\DB" folder.

  2. Copy all the files from the DB1.zip attached file to %sysdrive%\program files\intel\amtconfServer\Db.

  3. Now run the upgrade for Out of Band Management 6.2.


Note: The attachment ZIP is password protected. The password=  1



Hopefully the information provided here will resolve all issues stemming from this error.  Updates will be made when possible as additional details are known on the sources of this issue.



NOTE: To obtain the files mentioned in this post, please see the following link: