Jump to content


  • Windows-Noob logo

    Welcome to windows-noob.com!

    Logging in will allow you to download scripts used in the guides.

    If you came here looking for the Endpoint Manager step-by-step guides then please start here.

    Register for free and ask your questions in our forums.

    1702 Install Behavior check running exe's

    itrider
    By itrider,
    Has anyone successfully tested the new pre-release "install behavior for applications"?  I turned it on, created a couple new applications and set the install behavior to check for "outlook.exe" or "winword.exe". I cannot get clients to test successfully. I have checked logs and they confirm that it detects the app running, but the display does not show it for the failed section.  Anyone successful on this feature?

    RBAViewer crashing - KERNELBASE.dll

    AdminMatt
    By AdminMatt,
    We are running Config Man 1602.  When running the RBAViewer application that comes with the Configuration Manager Tools, using the Run As button will work fine if the user you are looking up is a full admin.  Every other user, or user that part of a group crashes the application... every time.  The Event Viewer (first quote) and then the application popup (second quote) shows the following:   I'm not aware of any updates to the ConfigMgrTools app.  Anyone else experience this?

    Windows 10 ADK - Should I update it?

    RLC-Andrew
    By RLC-Andrew,
    I currently have "Windows Assessment and Deployment Kit - Windows 10" version 10.0.26624 installed on my SCCM version 1702 Server. I believe when moving from 2012 to 1511, there was specific instructions at that time to install the version of ADK I'm running.  Possibly, because the newest version at that time had bugs related to win 10. Everything is running fine, patching works, OSD still works.  All is well.  So should I leave the old ADK version alone, or should I update it?  I cant

    Win 10 1607 Language Interface Pack issue

    simulacra75
    By simulacra75,
    Hi there Seem to have a problem with Language Interface Packs and Windows 10 1607 in a Task Sequence deployment. I've followed the guide on this site and that part seems to work (at least partly). Date/Time is displayed in the language of the LIP I installed (Chinese Traditional) but if i launch Windows Explorer, for example, the menus and labels are all still in English. If, however, i run a Task Sequence that installs the OS in English and manually apply the LIP after the TS complete

    Best Practice - Management Points

    SMSNewb
    By SMSNewb,
    Hello, I'm looking for some best practice advise regarding adding additional management points. Currently, I have a single SCCM server for all my roles.  I only have 1 site. I have an offsite office that connects via vpn to my site.  I was going to put a distribution point out there and was considering a management point as well. Is it best practice to only have management points on you main lan at your primary site? Or would things be okay if I put a management point in my office

    SCCM 1702 - MDT of Windows 10 Enterprise - en-US instead of GB

    Master-VodaWagner
    By Master-VodaWagner,
    I have applied the MDT approach using this guide and accepted the standard unattend.xml settings etc but when I want to select or install the GB language pack the install fails with error code: 0x80070002  <--- I cannot seem to find any additional log files to help with this error   My unattend.xml script is: <?xml version="1.0" encoding="UTF-8"?> -<unattend xmlns="urn:schemas-microsoft-com:unattend"> -<settings pass="oobeSystem"> -&

    SCCM 1702 & Win10v1703 deploy - "Just a moment"

    itrider
    By itrider,
    I have started testing PXE image deployment of Win10v1703x64.  Now that I have fixed my boot images (it upgraded them, but all my OS images were still pointing to the old ones), it deploys successfully.  However, I do have one quirk.  After the 2nd reboot where it would start to "Setup Operating System" and configure the client, I only see a blue screen that says "Just a moment".  Some other forums also have people with this problem.  The tasks appear to continue in the background, but I cannot

    My 1702 upgrade seems to be stuck. What do?

    Admiral Awesome
    By Admiral Awesome,
    Hi, I had to update my SCCM environment to 1702 due to the Office 365 update bug. The upgrade went okay until the install procedure copied the new x86 and x64 boot images. Now the installation seems to be stuck for around an hour (nothing happens in cmupdate.log) These are the last messages my SCCM delivered: INFO: Default SMS_BootPackageImage instance for x64 already exists. Updating the instance now.    CONFIGURATION_MANAGER_UPDATE    28.04.2017 14:45:55    11116 (0x2B6C) INFO

Portal by DevFuse · Based on IP.Board Portal by IPS
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.