Configuration Manager Software Center Organization Name not changing in some of the client machines

Sometimes you might face a scenario where some of your clients may showing wrong Organization Name under Software Center. Sometimes, initially you have mentioned the Organization Name with wrong spellings or sometimes you need to modify the name. But whatever the changes you are doing in Agent settings wont reflect to some of the clients after the modifications even after get the agent policy updates. Even if you tried to Uninstall the Configuration Manager Agent and reinstall it back won’t solve your issue. This issue which I have mentioned, I faced with Configuration Manager 1610 and with Client version 5.00.8458.1007 and specially when I Enable the “New Software Center”. The reason why specifically with “New Software Center” is when I rollback the Software Center to old one, the name appears to be correct and it takes from Agent settings details.

Below is the General Location where we change the Organization Name and its “New Software Center” Feature.

clip_image001

Check the Below Screen where it shows my previous Organization Name. Earlier I was using the Organization name as “Tes123”. But later I changed it to “Infront SL” as shown above. However, one of my client (Windows 10) did not change its Software Center Organization Name and even the colour of it. See the below screen.

clip_image002

clip_image003

clip_image004

So above is the simple trick I did to re-correct it. After the changes it started to show the correct name of my Organization.

clip_image005

Need to verify is this an intermittent problem which will rarely occur or not. Need to alert this further.

So you can either open the “GetBrandingInformationAsync” file in Notepad and change the company name and the rest of the fields you want or you can simple delete the folder (.cache) and reinstall will correct your changes.

VISUAL STUDIO 2008 SHELL INSTALLATION FAIL ON SCSM AUTHORING TOOL PREREQUISITIES INSTALLATION

clip_image001

Even after you download and install the given files, still the Installation will remain stop without continuing to nest step. So what you have to do is, after you install the Microsoft Visual Studio Shell 2008, Go to the install folder of the Visual Studio as shown below.

clip_image002

Explore the Folder and Run the vs_shell_isolated.enu.exe again.

clip_image003

Click Next and continue the Visual Studio 2008 Shell SP1.

clip_image004

Accept the Agreement and Click Next.

clip_image005

You will see the installation status as below.

clip_image006

Click Finish to complete the Visual Studio 2008 DP1 installation

clip_image007

With the completion of above, try to install the SCSM Authoring Tool Installation and you will be able to complete the installation as follows.

clip_image008

clip_image009

clip_image010

Configuration Manager Hotfix Got Stuck on “Prerequisite Check Passed”

Recently when I was upgrading my Configuration Manager 1606 to 1610, suddenly the ConfigMgr server got stuck with “Checking Prerequisites” state for couple of days. Initially I thought it will be ok in few hours but never finished the process until I started to figure it out. Below screen shows the state where it got hang.

 

Before you go further, “PLEASE NOTE THAT IF YOU ARE NOT SURE WHAT IS EXACTLY HAPPENED BEHIND THE SEEN, DONT DO THE FOLLOWING STEPS. THIS WILL LEAD YOU WITH

FEW OTHER ISSUES WHICH CAN BE REALLY HARMFUL FOR YOU. BETTER TAKE BACKUPS AND EQUIPPED WITH EVERYTHING TO OVER COME IF ANYTHING SERIOUS HAPPEN”.

The below scenarios happen in my test lab and after trying all the options I took the below steps to get  out from the trouble. So if you going to do it, take your own risk and do. I am just sharing this as an option.

different people will see this in various angles but I just show case you what I did. Smile

 

clip_image001

So Basically here what I did. in my case the Hotfix update pack was already downloaded which was located in a folder in the “SCCM Install Location\EasySetupPayload” directory as shown in below.

 

clip_image001[5]

Next what I did was i just Identified the exact Update which was stuck using the above screen. Though it was little tricky to identified the correct folder, i did several attempts for that comparing time of the folder creation and etc.

The reason is, the above folder name has random naming concept which is really hard to match.

 

After the figured out the exact folder, then U used the SQL Server Management Studio and ran the following query to find the record for this particular package from my SCCM database:

SELECT * FROM CM_CCL.dbo.CM_Updatepackages

ORDER BY DateReleased

CM_CCL.dbo was my DB name in ConfigMgr… So you can replace it with your name.

After I executed the query, based on the initial identification which I did in “EasySetupPayload” directory, i figured out the correct name in SQL results too.

 

clip_image001[7]

 

After verify the name of the PackageGuid, I ran the below command to delete the Package which Stuck in Prerequisites mode. I have used the below command for that.

DELETE FROM SCCM_Database_Name.dbo.CM_UpdatePackages
WHERE PackageGuid=’91406b1d-7c14-42d8-a68b-484be5c5e9b8′

 

Note- (Replace SCCM_Database_Name and the PackageGuid with your own details)

 

 

clip_image001[9] 

After verify the completion of the deletion, I then hit refresh on my ConfigMgr console and the problematic hotfix update pack disappeared from view.

Finally I just restarted the SMS_EXECUTE service and refresh the view again verify the service updates are started to download again or not.

 

clip_image001[11]

Unable to Download the Software- Configuration Manager

Hello,

In configuration Manager, when you are dealing with Application delivery via Software Center, there might be a certain case where you will see the error message stating that ” There is not enough temporary space reserved to download the software. You can use the Configuration Manager Control Panel to adjust the available temporary space”. Actually it might be a few MB file such as 37MB. But in Software Center it will show the Download Capacity as 6 GB or something. Huh.. Confused?? It is pretty simple matter. Let me explain the reason for this.

clip_image001

The below I used an application call Vivi which is 37 MB size in reality but below shows as 6075MB. Due to the size it shows, the ConfigMgr Agent is not in a position to install it due to the temporary assigned disk space is not suffice. Increasing the size of the temporary space will let this to install properly, but in reality this is not an solution.

clip_image002

The reality is that the 6.75 MB has taken as the entire packages of the Content Store location in SCCM. Under main folder I was having few other installers which are very big in capacities. The agent assumed and taken all these installers files capacity together as a one file size and showed in Software Center. You can refer the below screen. This was due to the so many installers files were in the same Folder which this ViVi app content was exist.

clip_image003

After I segregate the installers in to different folders and when I redeploy the same app, it was showing the correct file size as below. Due to this SMS Agent Temporary Space also no need to adjust and just Click the installation to complete.

clip_image004