Configuration Manager Web Frontend Update 1.0.4

This update addresses a few bugs that people have encountered since the last update. If you already have the frontend installed download the update for your version of ConfigMgr. Updated full versions are also available below.

Change log

  • ConfigMgr 2012 and 2012 r2 supported under same installation.
  • Initial inventory scan for sites with a large number of clients now works.
  • Added database prefix option for sccm installations that use SMS_<sitecode> or something else rather than the default CM_<sitecode>.
  • Added a debug logging option.

Downloads

Installation

To perform this update run update.ps1 in an elevated Powershell session.

Advertisements

31 thoughts on “Configuration Manager Web Frontend Update 1.0.4

  1. Pingback: HASMUG 2014 |M1 – System Center News & Updates | Houston Area Systems Management User Group

  2. Ron

    Scott (or anyone),

    Do you have problems displaying the webconsole via IE8? I seem to be getting JS related errors when trying to load the site via IE8. Was wondering if this was an issue on my part or incompatability with IE8.

    Thanks,
    Ron

    Reply
    1. skeiffer Post author

      I did not attempt to add any legacy IE compatibility with regards to the html, css, or js. It might work on IE9 but it will work on IE10+, firefox, and chrome.

      Reply
    2. MikeM

      Stepping through the install having one small issue. “All instances of the objects that are related to the assigned security roles” is greyed out and cannot be selected. Thoughts?

      Reply
      1. skeiffer Post author

        That should not be the case, Make sure the user you are logged into the console with a user that is the full administrator.

      1. spbreed

        Thanks for your reply.
        I am not looking to replace MDT WFE functionalities with this.
        I am trying to understand native SCCM 2012 capabilities to do OSD via PXE service point is supported by CM Webfront end or not.

      2. skeiffer Post author

        At the moment no aspects of OSD are supported. Unfortunately it is out of the scope of the project due to the nature of OSD and the potential damages a mistake could cause.

  3. Gary O

    I’m having trouble — CM FrontEnd thinks I have an configuration error – it doesn’t like my FrontEndAdminGroup, it says the first word in the group name is an unexpected token. This is an AD group, correct? What format should it be?

    Reply
  4. Svein-Ove Urdal

    hello,, stumbled over this console for the sccm 2012 r2 :-), have installed it but i can not get the appications to turn up in the console.. (everything else Works as a charm).. any idea what i have missed ?

    Reply
    1. Cory Freeman

      I got past the above error, and everything appears to be working except all the tools when I click on them it does nothing. Thoughts?

      Reply
      1. skeiffer Post author

        The tools are launched by a Java applet. With the newish java security settings it can be a pain to get it running. Set the java security the medium and add the site url to site list. After doing that it should work with a few warning messages.

  5. Cory Freeman

    Updated Java and that has resolved the above issue… Now the only issue I have left appears to be getting the rest of my tech team logged in… When I did the install I created a group stuck the users in that group but they can not login. Am I missing something or is there something I need to add to SQL/configmgr to get them in… They just get Access Denied.

    Reply
    1. Cory Freeman

      I just noticed if they are not in nested group and I add user directly it works but all the users get teh admin button I don’t want them to see that how can I only show that button to the full sccm admins only?

      Reply
      1. skeiffer Post author

        The group you created for the frontend is only for the administrator. Access to the site otherwise is completely dependent on sccm’s RBAC rules. On the admin page you will see all the AD groups that have rbac rules defined from there you can enable their access and select which collections show up on the page. If no groups are listed then you need to create a new rbac rule for an ad group that contains those users.

  6. kael187

    Hello
    In advance thanks for the answer.
    I installed the server and therefore also the CM WebFronted and no longer displays the tab INFORMATION, I reviewed the log and displays the following message: “The incoming request has too many parameters. The server supports a maximum of 2100 parameters. Reduce the number of parameters and resend the request”.

    Reply
      1. kael187

        Hello

        here the log…

        System.Data.SqlClient.SqlException (0x80131904): The incoming request has too many parameters. The server supports a maximum of 2100 parameters. Reduce the number of parameters and resend the request.
        at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
        at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
        at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
        at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
        at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
        at System.Data.SqlClient.SqlDataReader.get_MetaData()
        at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
        at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
        at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
        at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
        at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
        at System.Data.SqlClient.SqlCommand.ExecuteReader()
        at FrontendDataLib.DataHandlers.ConfigMgrSqlHandler.GetComputerDataItems(IReadOnlyList`1 ids, SqlConnection connection, String name, String dynamicName, String path)
        at FrontendDataLib.DataHandlers.ConfigMgrSqlHandler.GetComputersData(List`1 ids)
        ClientConnectionId:47e00205-7252-4d6e-9f58-5a3856df11c5

        I install the SQL server Express manual on new OS installation and configure the access whit users SCCM and the log no change.

        Thank you…
        Arturo Panca

      2. skeiffer Post author

        can you got C:\Program files (x86)\CMFrontend > right click on frontenddatalib.dll > hit properties > goto details tab and then tell me what the file version is?

      3. kael187

        This is the log for access

        DATABASE = 172.16.1.134
        WEBFRONT = 172.17.1.116
        —————————————————————————————————————————————————————-
        Date 02/11/2015 07:29:06 p.m.
        Log Windows NT (Security)

        Source Microsoft-Windows-Security-Auditing
        Category (12810)
        Event 5156
        Computer DATABASE

        Message
        The Windows Filtering Platform has permitted a connection.

        Application Information:
        Process ID: 1816
        Application Name: \device\harddiskvolume3\program files\microsoft sql server\mssql11.mssqlserver\mssql\binn\sqlservr.exe

        Network Information:
        Direction: Inbound
        Source Address: 172.16.1.134
        Source Port: 1433
        Destination Address: 172.17.1.116
        Destination Port: 49273
        Protocol: 6

        Filter Information:
        Filter Run-Time ID: 65708
        Layer Name: Receive/Accept
        Layer Run-Time ID: 44

      4. kael187

        skeiffer another question how many clients support the solution. I have proccess 3000 clients. or the sql express maybe no support many clients?…

      5. Arturo Panca

        hello

        I found the problem the SQL server express only support less 2100 paramaters on the query, if the query resolv more the 2100 parameters do not show the result.

        I sorry for my english.

        Encontré el problema todo era porque el SQL express no soporta mas de 2100 parámetros en consulta que se configura en la base de datos tuve que ingresar colecciones que no excedan los 2100 objetos uno por uno para no incurrir al error, espero que entiendan el resultado de mi resolución para este caso, gracias.

  7. Arturo Panca

    The file version is 1.0.0.2
    other questions have again the same events “The incoming request has too many parameters. The server supports a maximum of 2100 parameters. Reduce the number of parameters and resend the request”, if I implemented the solution with a SQL Server and not with express it would be no problem. Apparently the problem is the limitations that gives me a SQL Express, remember that administer client computers that are over 3000.

    la versión del archivo es 1.0.0.2
    otra consulta tengo otra vez los mismos eventos “The incoming request has too many parameters. The server supports a maximum of 2100 parameters. Reduce the number of parameters and resend the request”, si implemento la solución con un SQL Server y no con un express habría problema alguno. Al parecer el problema son las limitaciones que me da un SQL Express, recuerda que los equipos clientes que administro son mas de 3000.

    Reply
    1. skeiffer Post author

      You are using the wrong version. The current version is 1.0.0.4. If you update to the current version (released 01/2014) your issue should be fixed.

      Reply
      1. Arturo Panca

        I just apply the update to version 4 will be monitoring events. Thanks you.

        acabo de aplicar la actualización a la versión 4 estare monitoreando los eventos. Gracias.

  8. Dave Stagg

    Hi Scott – thanks and kudos for sharing your talents with the ConfigMgr community. I have an off-topic question (sorry!) – I can across one of your old posts on myitforum http://myitforum.com/myitforumwp/2012/01/04/automation-preventing-user-interaction-and-resuming-execution-after-restart/ and was hoping you might still have the AutologonMiniTS.zip source available to download? (The link there is broken.) It would really help me with a current project. Thanks again!

    Reply

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s