WI 15048: SCCM Control Panel Applet missing – Command line to run it

With the improvements to the control panel the Configuration Manager Control Panel Applet (CPL) has disappeared.  To add insult to injury the default location of the SCCM client is not indexed nor in the system path.

Open the Configuration Manager CPL

c:\windows\ccm\SMSCFGRC.cpl

SMS back from the dead ūüôā ¬†I always wondered if the files were not renamed due to all the white and black listing applications that would have to be updated… or if it is just because that is how they were checked into the coding suite.

 

Best

Client Health : Group Policy initiated Based Script – All those core fixes still work great with SCCM Current Branch for FREE!

It came to my attention recently in a Twitter Post by Troy Martin that client health is still a thing.  It is silly companies are trying to take your money to fix clients for SCCM by doing things that have been free since 2005 and which SCCM CB fixes really well. Here is a table from the twitter post that is pretty good

c6em6iiuwaa7jkb

To add to the detail of the things you can get from the community.  Here is my updated post from MyITForum in 2008.  I picked up the torch in 2006 and ended in 2010.  Lots of great fixes out there that still work!  Just like the Sunshine and Daises.  Client Health is really easy now and free!

I am ACTIVELY looking for a copy of the script Public_SMS_CLIFIX_V4.21.vbs.txt was the last one I released.  All thanks to @Mike Terrill (www.miketerrill.net) for dredging up 4.18

CLIFIX_Public_V4_18

Below is a listing of features in a reworked version of Dudeworks (Thanks Rob and Brian), 1E, et al. (see bottom for longer list) start up scripts.¬† I recently became aware of Chris Stauffers Client Health Checker v1.2.¬†¬† My script focuses on workstation health, Chris‚Äô focuses on SMS health.¬† It is my hope in 2009 to combine these two if it seems intelligent to do.¬† Hopefully we can have this all together in early 2009.¬† Be great to present and then for everyone to tear apart at MMS… anything is possible.¬†

Reminder: this is not finalized.  It takes a community. Please feel free to post updates in the forums.

Overview

Workstation Client Health maintenance is a continuous process that must be maintained.

Overview

Workstation Client Health maintenance is a continuous process that must be maintained. The following document gives an overview on how to fix several common workstation issues.

Note: The original Link no longer works.  I am actively looking for any version 4.18.  CLIFIX_Public_V4_18

CliFix GPO startup script :- Can NO LONGER be downloaded from here http://myitforum.com/cs2/blogs/scassells/Public_SMS_CLIFIX_4.19.vbs.txt

In an effort to reduce the amount of common workstation issues I have developed a script to check and change the following common issues. This script is to be run via GPO startup scripts. This requires the script to work as the system account and have intranet connectivity. Both are accomplished by running as a GPO. Script Requirements

  1. Script must be in a location where the computers system account has access. Usually on your domain controller ex. \\FQDNDomain\sysvol\ FQDNDomain\
  2. sc.exe must be present for full successful run.
    1. Either in the run path
    2. system32
    3. system32\DLLCache
    4. Note: there are multiple versions floating around in the average environment
  3. regsvr32.exe needs to be present
  4. %systemroot%\system32 needs to be in system path
Script Settings

All, unless I missed some, sections of the script can be turned on and off in the top of the script. Please review the script as some features will fail without modification.

Please Review the following CONFIG SETTINGS Variables:

  • SMSVersion
  • ConfigMgrVersion
  • WKS_ASSIGNSITECODE
  • WKS_CacheSize
  • WKS_LocalAdminGroup
  • WKS_admACCT
  • RegPath
  • strWebAddress
  • StrCCRServer
  • strCCRSiteCode
  • CCMSetUP
What the Script Does
  1. Checks to make sure the script has not run in X many hours.
    1. Example if X = 12 the script will not run again until at least 12 hours after the last occurrence.
    2. This will prevent a slow down on multiple reboots.
  2. Sets DCOM permissions to be correct for SMS / SCCM configuration
  3. Checks to make sure System Path has the 3 required windows paths enabled. (does NOT use WMI or require a restart to change values)
    1. C:\windows
    2. C:\windows\sysetm32
    3. C:\windows\system32\wbem
    4. Also removes %systemroot% from path replacing it with correct full path value
    5. If one of the 3 paths is missing, it will parse the full path removing duplicates and adding a,b,or c to the beginning of the path statement leaving all else unchanged.
  4. Check to see if sc.exe exists in the run from directory and if not in the system32 directory
  5. Checks to see if this script is run on a workstation or server. If a server kills the script
  6. Checks to make sure the correct local admin group is present (value is set in header of script)
  7. Checks WMI service to see if it is set to auto and running. If not executes sc.exe to start the service.
  8. Attempts to connect to WMI object
  9. If the WMI object connect fails
    1. Attempt to do a repair (if no previous status is present in the registry and approved via script switches)
    2. Attempt to do a rebuild (if ‚Äėrepair‚Äô status is present in the registry and approved via script switches)
    3. If both the above have failed then do nothing and report major error
  10. Checks to see if Admin$ is present, if not forces existence via WMI
  11. Checks to see if msxml3.dll is registered, if not forces existence via WSH
  12. Checks to see if Qmgr.dll and qmgrprxy.dll are registered, if not forces existence via WSH
  13. Checks to see if OLEAut32.dll is registered, if not forces existence via WSH
  14. Checks to make sure the following services are set to appropriate Status and Mode
    1. RPC
    2. WMI
    3. Firewall/ICS
    4. Server Service
    5. Remote Registry
    6. BITS
    7. Windows Update Services
    8. Terminal Services
    9. Windows Installer
    10. Note: You may want to review the settings for your environment on each of these services. All of the above services are set to default and either Manual or Automatic.
  15. Check the SMS version
  16. Checks the CCMExec service
  17. If SMS is not correct version can be forced to do an install
    1. Needs Review
  18. If the all of the above test passed without issue you have a healthy workstation. The following two checks are for SMS.
    1. Check log file last update time. If the PolicyEvaluator.log file has not been modified in past 14 days do a repair of the client.
    2. Check client assignment. If no assignment set new site code based on AD boundaries in which the client is present.
      1. Note: Some people may want to disable this as it relies on AD
  19. If any fixes above had to be preformed
    1. Check the advanced client state. Which client policies have enabled.
    2. Check the cache size
    3. Send a Client Configuration Request (CCR) to have client installed
    4. Run CCMSetup from the install share on the server.

Note during this script several forms of reporting, logging, and information submitting have been preformed. The standard methods of reporting are:

  • Event log
  • Log file in the %temp% directory for the account used to run
    • GPO = C:\windows\temp
  • Reporting to a website that submits client status to a SQL table.
    • Future WebPost on how to do this

Other verbose methods include:· Two levels of command line reportingo Log to Command lineo Verbose to command line· network share copy

Future Additions:

Area’s that need improvement

References:

·         MyITForum Forum: http://www.myitforum.com/forums/tm.asp?m=107044 ·         1E: http://www.1e.com ·         Chris Stauffers soon to be reviewed: http://myitforum.com/cs2/blogs/cstauffer/archive/2008/06/13/client-health-check-script-and-scheduled-task-version-1-1-release.aspx ·         Brian Mason: Original Author of CliFix ·         Rob Olson: Original Author of CliFix at http://www.dudeworks.com ·         Greg Ramsey:http://myitforum.com/cs2/blogs/gramsey/ ·         Steve Pruitt: http://myitforum.com/cs2/blogs/spruitt/ ·         And the MSSMS list http://www.myitforum.com

 

Creator Update: Coming very soon. Slow Ring Windows Insider released build 15048

https://blogs.windows.com/windowsexperience/2017/03/03/announcing-windows-10-insider-preview-build-15048-for-pc-and-build-15047-mobile/#xhFYJ2X3MUCgu2HP.97

15048 has been released to the Slow Ring of Windows Insiders.  This means unless a huge bug is found we will have a creator edition release in about a month.  Expect several more builds to remediate issues found in the larger slow ring.   Cadence about upgrades for consumer upgrades will increase.

Keep in mind this release will be Current Branch (CB).

Current Branch for Business (CBB) will be released after CB has been in the wild for a few months.¬† Think when the first major cumulative updates have been applied to CB.¬† 1607 (anniversary edition) went CBB 4 months later. ¬†Enterprises have a bit more time to test. ¬†Check out the Windows Insider for ITPRO –¬†https://insider.windows.com/home/itpro

CB, CBB, LTSB release dates

https://technet.microsoft.com/en-us/windows/release-info.aspx

Marriott.com Too Many Redirects and Access Denied on landing page

From time to time the http://www.marriott.com website appears to die.  The errors may show for login or on search.

marriott-redirect-1

Google, Firefox, and Chrome all state “Too Many Redirects”. ¬† This means the cookies have become stale and are causing issues.

The easiest solution is to remove the cookies for the effected website.

Chrome

  1. Open Chrome
  2. chrome://settings/cookies
  3. Search for the website that is having issues
  4. marriott-redirect-2
  5. Remove all shown
  6. Done
  7. Reload the page .. should still give you the error. Reload forced CTRL+F5 (this reloads without using local cache)

Chrome Cookies Location

Settings > Show Advanced Settings > Privacy > Content Settings > Cookies > All Cookies and Site Data
%localappdata%\Google\Chrome\User Data\Default\Cookies

Safari: “Could not open the page, too many redirects”

This might happen if you visit a page that’s been set to open another page, but the next page is instructed to go back to the original page.

This issue can be caused by the website you’re trying to view. Safari might be able to open the website at a later time, when the website’s redirect problem has been corrected.

This issue can also happen if redirect information has been cached after it’s no longer needed. In some cases, removing related cookies and cache in Safari can resolve repeated redirects:

  1. Safari, choose Safari > Preferences.
  2. Click the Privacy icon to view Privacy settings.
  3. Click the Details button that appears under the Remove All Website Data button.
  4. Search for the name of the website that you are trying to view.
  5. Click the Remove button.
  6. Close the Safari Preferences window.

If the issue continues, repeat the steps without searching for a specific website. Click the Remove All Website Data button to remove all of your cookies and cache files. If this does not resolve the issue, contact the owner of the website you’re trying to view for additional help.

Windows Store Install Error 0x803F8001

While playing around with the most recent Windows Insider build I ran into an application that was receiving the 0x803F8001 Error.  Ironically, I have not been able to find exact error code in online documentation.  Instead I am going to write a short summary of methods to work with the Windows Store to resolve a multitude of issues including this one.

store-feedback-install-error-0x803f8001

Windows EventViewer Error Details

Fault bucket , type 0
Event Name: StoreAgentAcquireLicenseFailure1
Response: Not available
Cab Id: 0

Problem signature:
P1: Update;Microsoft.WindowsStore_8wekyb3d8bbwe
P2: 803f8001
P3: 14393
P4: 576
P5: Windows.Desktop
P6: N
P7: 
P8: 
P9: 
P10:

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_Update;Microsoft_c92bdd60e6ccf0dc89ec13246a78b39b61a9bae_00000000_45ca645c

Analysis symbol: 
Rechecking for solution: 0
Report Id: 73e2874a-d67b-11e6-9ae3-e4b318276f42
Report Status: 4100
Hashed bucket:

Ahh, StoreAgentAcquireLicenseFailure1.  Access denied or Corrupt files.  Interesting.  Lets dig further!

Windows Store TroubleShooter

https://support.microsoft.com/en-us/instantanswers/69e76f90-d54c-44cf-9851-c2d1542790db/run-the-troubleshooter-for-windows-apps 

No Joy but it did do things… what are those things?

Reset the Windows Store

  1. Open Administrator Command Prompt
    1. Winkey + X
    2. Command Prompt (Admin)
  2. WSReset.exe
    1. Resets the Windows Store (will close and reopen the Windows Store)

No Joy but now I feel better!

Register the Catalog Manifest again

Run the following from a Admin Command Prompt (see above on how to open one)

PowerShell -ExecutionPolicy Unrestricted -Command "& {$manifest = (Get-AppxPackage Microsoft.Windows
Store).InstallLocation + '\AppxManifest.xml' ; Add-AppxPackage -DisableDevelopmentMode -Register $manifest}"

Just a note, this won’t work if the store is open. ¬†So close the store ūüôā

Error if Store is Open

Add-AppxPackage : Deployment failed with HRESULT: 0x80073D02, The package could not be installed because resources it
modifies are currently in use.
error 0x80004004: Unable to install because the following apps need to be closed
Microsoft.WindowsStore_8wekyb3d8bbwe!App.
NOTE: For additional information, look for [ActivityId] 35681ba7-696a-0003-86d6-69356a69d201 in the Event Log or use
the command line Get-AppxLog -ActivityID 35681ba7-696a-0003-86d6-69356a69d201
At line:1 char:97
+ ... fest.xml' ; Add-AppxPackage -DisableDevelopmentMode -Register $manife ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 + CategoryInfo : NotSpecified: (C:\Program File...ppxManifest.xml:String) [Add-AppxPackage], Exception
 + FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand

Ironically the steps above did not resolve the issue in question.  What did?

Fix: Uninstall and Reinstall

Uninstall the app from the start menu.  By right click and uninstall

store-unistall-feedback

Open the store and go shop for the app again.

Be aware, this was a minor application but an app with lots of configuration files will all be reset to default.

So what is actually broken?

This leads me to believe there is a corrupted install somewhere in your local user profile.

C:\Users\shaun.cassells\AppData\Local\Packages\Microsoft.WindowsStore_8wekyb3d8bbwe\LocalCache

That means it is either a stuck transfer via BITS or Corrupted access on the local device.  Why am I leaning towards access?  Because the app still opens and runs fine but I cannot update it.

I am going to keep looking for a direct definition of the error code and the access denied issue