Jump to content


Bram

Established Members
  • Posts

    24
  • Joined

  • Last visited

Bram's Achievements

Rookie

Rookie (2/14)

  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Week One Done Rare
  • One Month Later Rare

Recent Badges

0

Reputation

  1. Thanks for the feedback, tested gpupdate and it completed successfully. Also double-checked with Test-ComputerSecureChannel: VERBOSE: Performing the operation "Test-ComputerSecureChannel" on target "SCCM02-SHA". VERBOSE: The secure channel between the local computer and the domain company.local is in good condition. Meanwhile I've upgraded the main site to 2203 hoping there was maybe an undocumented bug fix but the secondary site is still failing at the domain member check.
  2. I'm currently trying to set up a new secondary site with SCCM 2111 on Windows Server 2019 and the prerequisite check fails with: [Failed]:Configuration Manager site server components must be installed on computers that are members of a Windows domain. In ConfigMgrPrereq.log this is noted as: INFO: Failed to get Active Directory membership information for computer SCCM02-SHA.company.local with 53. SCCM02-SHA.company.local; Domain membership; Error; Configuration Manager site server components must be installed on computers that are members of a Windows domain. The server is definitely domain joined, the firewall disabled and all other checks pass without any issue even the 'Check to see if the site server has permissions to publish to Active Directory.' Does anyone know how being domain-joined is checked? I tried finding out with Procmon during the check but couldn't find anything relevant. Is there any way to force the secondary site installation?
  3. Thanks, for submitting feedback at MS, really appreciated. I've deployed a new CMG now which is indeed probably the easiest solution.
  4. Everything is green except for the first item 'Check the CMG Service is in a ready state'. State of the CMG Service is '2'. CloudMgr.log is showing following issues: ERROR: Service brokencmg does not exist. ERROR: Exception occured trying to change service status brokencmg: System.InvalidOperationException: VM scale set does not exist for service.~~ at Microsoft.ConfigurationManager.CloudServicesManager.ChangeDeploymentStatusTask.StartDeployment(). ERROR: TaskManager: Task [ChangeDeploymentStatus for service brokencmg] has failed. Exception System.InvalidOperationException, VM scale set does not exist for service.. In the console, the deployment model of the broken CMG shows 'Virtual machine scale set' while the conversion did not complete and the old classic services are still there in Azure.
  5. The conversion of a classic CMG to the virtual machine scale set model failed. In the end I found out why: Microsoft.KeyVault was not yet registered as a resource provider in the Azure subscription... But now we're stuck with a broken CMG that has status 'error' - unable to connect to the cloud service. The broken CMG service name uses our own domain and wildcard certificate: brokencmg.company.com. Just wondering if I can just spin up a new working cmg under the same domain newcmg.company.com and then just point the CNAME record of the broken one to the new cloudapp service in Azure so both URLs keep working?
  6. About two days after the initial setup, I can complete the wizard without any extra changes in SCCM or Azure. I contacted another person with the same issue and they also just waited a couple of days and it worked.
  7. We're trying to set up a Cloud Management Gateway and following the regular guides all works fine until one of the last steps, the actual creation of the CMG in Azure. At the beginning of the wizard I just log in to my Azure admin account that I used to set up all other parts. The wizard then auto-populates all Azure fields and finds the correct resource group. When clicking finish it shows the error: Error occurred when granting Contributor permission to the Azure AD app for resource group RG-SCCM-CMG. For more information, see SmsAdminUI.log When checking SmsAdminUI.log we see: Hyak.Common.CloudException\r\nInvalidAuthenticationTokenTenant: The access token is from the wrong issuer 'https://sts.windows.net/f8cdef31-xxxx-xxxx-xxxx-xxxx/'. It must match the tenant 'https://sts.windows.net/aa3c372d-xxxx-xxxx-xxxx-xxxx/' associated with this subscription. Please use the authority (URL) 'https://login.windows.net/aa3c372d-xxxx-xxxx-xxxx-xxxx' to get the token. The guid starting with aa3c372d is indeed our correct tenant ID. I have no idea where the one with f8cdef31 comes from. I've search for this guid in our Azure subscription but nothing pops up. Also in SCCM under Azure Active Directory Tenants only the tenant with aa3c372d is shown. Anyone an idea of what could be wrong?
  8. You could try the vbs script posted in the following topic: https://social.technet.microsoft.com/forums/en-US/e0bd29ad-adf5-4c33-a2f2-740df8cc6c32/applications-not-visible-in-software-center
  9. Found the issue: it's a known bug https://social.technet.microsoft.com/forums/en-US/e0bd29ad-adf5-4c33-a2f2-740df8cc6c32/applications-not-visible-in-software-center
  10. Hi Peter, I didn't seem to help. Afterwards the Software Center is empty, also the installed application list which was populated before by manually clicking 'install' in the Client Center is empty. When now clicking 'install', they're added again to the installed list.
  11. This is very weird. I have one laptop which doesn't show available software in the Software Center although it's in the same device collection as all our other devices. The device shows up with a heartbeat as 'active' in the SCCM console. I tried repairing the client software but that didn't help. When using Client Center for CM, under Software Distribution -> Applications. All the available/deployed applications show up but they have no status. (screenshot below) I can right-click each of them and select install which correctly installs the application. The software then also shows up in the Software Center under 'installed software' so there is no issue with our distribution points. Anyone seen this issue before?
  12. Damn, why didn't I think of this I've moved my reboot part to the vbs script and all is working fine now. Thanks Peter.
  13. Hello, I'm trying to add a remove option in our Software Center for Office 2013. I'd like to use the OfficeScrub script to remove the software and do a reboot afterwards. The remove-office.bat script looks like this: :remove Microsoft Office 2013 suites cscript "C:\Program Files (x86)\Microsoft Office\uninstall\Offscrub13.vbs" ALL /Quiet /NoCancel shutdown /r /f On the client the Offscrub13.vbs file is available in the folder above. The bat script is available in the content and in the Office deployment options I've added: When clicking the uninstall button in the software center, after a few seconds the shutdown command triggers. So I guess it skips the uninstall line. Any reason why this happens? The bat script runs fine from command line.
  14. Sometimes the solution is too simple to see it I just added a second format & partition disk step to the sequence. This creates a temporary volume to download and run the bios tool. After the reboot the old format & partition step starts with the variables and everything is good to go.
×
×
  • 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.