Jump to content


All Activity

This stream auto-updates

  1. Today
  2. I joined just to say "THANK YOU!!" Super old thread but this has saved my sanity
  3. Last week
  4. If you (like me) have used Quick Assist in the past you might be disappointed to know that the built in Windows 10/11 app is going to be killed off in the coming days and replaced with Quick Assist from the Microsoft Store. If you start the Quick Assist app today you'll see something like this (taken from my Windows 11 computer). the text below is taken from the official announcement. Why is this a big deal ? Well for a couple of reasons namely... If you were supporting users in Windows Autopilot using CTRL+Windows key + Q, then that built in ability will be gone. If your users are Standard Users (and they should be) then they won't be able to install the app from the Store as it requires local admin permissions. Below screenshot is from a Windows 10 vm running as a standard user. If the computer you are supporting has Store app issues (and that's a common problem, for example store apps not working after a Cumulative update was installed and waiting on a reboot). The new app uses characters as well as numbers, and that might confuse some people Ironically, the new Store apps provided instructions say nothing about the fact that the user has to download the Store app to get support. Some think this is a good thing as it means only admins can install the remote assistance app, but I think it'll just push people towards alternatives What are your thoughts on this ?
  5. Introduction This video is a quick look at the Migrate to the cloud app. The Migrate to the cloud app is a Powershell based solution delivered via Software Center in Microsoft Configuration Manager, that takes your domain joined, ConfigMgr devices and migrates them to Intune management and converts them to Windows Autopilot devices in the process, all done without data-loss and minimal user interruption or downtime. You can check out the video here. I'll be posting a blog post or two covering how to implement this in your own environment, watch this space.
  6. Earlier
  7. select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.IPSubnets in ("xx.xx.xx.0") and SMS_R_System.OperatingSystemNameandVersion like "%workstation%" This is working thank you
  8. hi @rahill here's what I got from Microsoft ConfigMgr 2203 current branch Eval - https://aka.ms/MECM2203CB-Eval ConfigMgr 2202 technical preview baseline - https://aka.ms/MECM2202TP-Baseline
  9. hi Robert, do you require 2103 eval for Current Branch or will another (later) version do ?
  10. Once we have removed the DP role, what we should do with the content packages in the server disk ? In the case I need to do remove them manually what will be the best way? Should the server be removed also from the Boundary Group? Thanks
  11. Once we have removed the DP role do we have to removed the content packages from the server disk manually? In the case I need to do it manually what is the best process? The server should be also removed from the Boundary Group? Thanks
  12. you are right it doesn't work currently, Microsoft has been made aware of this i\ll update this once i know more
  13. Greetings, I am trying to access to Microsoft Endpoint Configuration Manager current baseline evaluation version 2103. The link https://www.microsoft.com/en-us/evalcenter/evaluate-microsoft-endpoint-configuration-manager no longer works it goes to the Surface Devices web page. Am I missing something or is this web page down? Your assistance will be appreciated, Robert
  14. I build new DP and set it up for pre-stage content but packages are not mark as successfully even after i run the pre-stage command On remote DP I have copy all of the pre-stage packages and run following command for each package ExtractContent.exe /f /P:X:\Prestage\Content\xxx28.pkgx When I check the prestage log file under SMS_DP$\sms\logs\PrestageContent.log I see following messages Sent xxxx28.5 package state message to site but after few days I still see same package in progress with following message Distribution Manager is waiting for package xxx28 content to be prestaged on the distribution point ["DISPLAY=\\DP\"]MSWNET:["SMS_SITE=xxx"]\\DP. You must manually prestage the package xxx28 on the distribution point before the content will be available. I also try following I have remove the Prestage tick from new DP but 2000 packages are still say Waiting for prestaged content Distribution Manager is waiting for package xxxxxxx content to be prestaged on the distribution point ["Display=\\xxxxxxx\"]MSWNET:["SMS_SITE=xxx"]\\xxxxxxx. You must manually prestage the package xxxxxxx on the distribution point before the content will be available. In Progress xxxxxxx All of the packages are already on the DP - I can see them in the content library application How do I force site server to mark these packages as successful
  15. Bringing up an old topic. I'm needing to do this same thing. We have Cert Authorities in both domains. However, the RootCA is from Domain A and the client cert is from Domain B. It's set up in a way that the chain from client cert in Domain B validates with the RootCA from Domain A. However, ConfigMgr won't recognize the client workstation cert as a valid cert, even though the chain looks right. Any ideas? I'd like to get this working. I've since created a MP/DP and working on SUP in Domain B, using all the proper accts from a document I've seen. That all works, but had to move my infrastructure over to EHTTP. Would rather be HTTPS Only. Now that I have the server in Domain B, could I go to HTTPS Only if I created the proper Web Cert in Domain B like is in Domain A? Lots of questions to be asked here. Do you need to place Domain B's Intermediate Cert anywhere? There isn't a lot of documentation out there around this. One thought I was going to bring up with our Admin who takes care of Cert Authority, is why not just have a RootCA for Domain B, instead of the RootCA being from Domain A and anything below be from Domain B. Thank you for the insight in advance. the client workstation change looks like this in Domain B: DomainARoot.com <--RootCA DomainBIntermediate.com <-- Issuing Intermediate in Domain B DomainBClient.com <-- Client workstation Cert
  16. I made this change "%windir%\system32\WindowsPowerShell\v1.0\powershell.exe" as I'm using the 64 bit version And in the script I changed "TSProgressUI.exe" to "Explorer.exe" and then it worked Sourced from: https://smsagent.blog/2016/02/19/prompting-the-end-user-during-configmgr-application-installs/ Hope this helps...after two years
  17. i don't have a lab in your state to test this on as mine already has bitlocker management enabled, so please go ahead and create a test bitlocker management policy, doing so will put in place things like bitlocker management services in IIS, back when this was first released in 1910 we had to run powershell scripts to get reports, but it's all integrated now
  18. No. Nothing. I thought that the reports would be visible by default since the upgrade. If they don't appear until you start enabling bitlocker management, then maybe that's my answer for why I can't see them.
  19. first things first, have you created any bitlocker management policy yet ? when you create your first policy it starts installing things, and maybe that's what you are missing
  20. Ah thanks for this. I'll take a look. I didn't get a notification for this for some reason (they are turned on), so sorry for the slow reply. I don't see the BitLocker category under 'Reports' at all. I know that we do not use PKI certificates, so having had a quick glance at your posts, I guess this could cause a problem down the line with using the integrated BitLocker features, but shouldn't the reports at least be visible since I upgraded to 2107?
  21. if DNS doesn't work then nothing will work, you need to fix DNS first and then deal with all the other issues.
  22. Just General Information If i change DNS address for sccm client apart from DNS port is there any other port need to be checked for sccm client to send its inventory to MP.Its not new DC just DNS services are installed and existing DC are in place which have DNS role so client now have new DNS entry along with older ones .After this DNS update client are now showing not active in Console more like its not able to resolve MP computer name nwo https://siteserver/ccm_system/request ,port 80 ,option=1216, code =12007 ,text=error_winhttp_name_not_resolved
  23. here's a video and blog post i did which covers Bitlocker reporting in ConfigMgr https://www.niallbrady.com/2020/01/08/learn-about-mbam-in-microsoft-endpoint-configuration-manager-version-1910-part-7-reporting-and-compliance/ https://www.niallbrady.com/2019/11/12/a-quick-look-at-reporting-in-mbam-integrated-with-microsoft-endpoint-manager-configuration-manager/ if these don't help you see your bitlocker reports then let us know
  24. Yes, there are at least 4 bitlocker repot within CM. No the report should be there BEFORE turned on bitlocker. You will need to review the CM reporting point logs to see what the deal is.
  25. I'm looking to use the built in BitLocker reports. https://docs.microsoft.com/en-us/mem/configmgr/protect/deploy-use/bitlocker/view-reports I am running config mgr 2107, so believe they should be there, but I don't see them. Does anyone know how I make them appear? I've only just enabled the Bitlocker Management feature. Is this a factor? We do not use config mgr to administer BitLocker but I'm hoping that I can still access the reports. It doesn't look like I have any new reports available since upgrading to 2107. Thanks!
  26. Client is upgraded no issue with upgrading the client, the only thing is that SMSCACHESIZE is not changing to 15% of the disk size. In the client.msi.log i see following message Cache Info already present. SMSCACHEDIR, SMSCACHEFLAGS would be ignored. How do I force the client to take new settings without re-installing it
  1. Load more activity
×
×
  • Create New...