User Profile
kwester-ebbinghaus-business
Iron Contributor
Joined Jan 27, 2020
User Widgets
Recent Discussions
ISSUE - cannot change my account's email address
Dear techcommunity staff, our company has been merged. I am looking for a way to change my email address. The account has been created by a work account. Fields to change email are greyed out. I would not like to create a new account as I would loose ownership / track of all conversations, history and notifications for topics and my contributions. What can I do?On-premises FSLogix Support for Partners revoked
Dear Microsoft FSLogix Team, this is not a technical support request. I am describing a changed behavior for the process of creating support requests, which now prevents Microsoft partners from doing so. Yesterday, I tried to open a support request for an FSLogix on-premises (not AVD) implementation. according to this guide (I am not aware about a newer reference) https://social.msdn.microsoft.com/Forums/en-US/14ea5f6f-760b-4ad2-83cf-23c3cbc1bcc4/how-to-open-a-fslogix-support-request?forum=FSLogix the business support is still responsible, and the customer needs to select On 21st of June it was not possible to submit any request using an MPN ID support contract. Today on the 22nd of June these contracts are entirely revoked. In both cases Partner Signature contracts are greyed out. Means MS Partner cannot longer open business support requests for FSLogix on-premises following the guide linked above. Will there be an update on the common guide or an updated blogpost on techcommunity, since technet is in read-only mode for this matter? Additionally, opening the ticket via phone is still possible but with caveats. The first agent declined to open the ticket via the described buckets and persistently insistet that FSLogix tickets belonging to the Azure category have to opened via the Azure Portal. This is not correct for the on-premises use of FSLogix according to the guide. I called again and the next agent was not hesistant to open the ticket in the Azure category. Although he faced a 12 minutes delay to open the ticket due to a problem with the internal system.Re: Server 2022 KMS host key bug; Can't activate Win10 Enterprise LTSB/LTSC
Armando_Rivera with the myriad of issues KMS are stunning. Mind that KMS, and so also ADBA are out of door. CSP (New Commerce Experience) licensing won't give you any KMS keys anymore which is a pity IMHO. KMS will reside for classic licensing models and big customers having EA(S). Also notice that service providers don't want to give you KMS keys anymore. So you must go down the route with MAK Keys and VAMT 3 from the lastet ADK to have centralized and easy management. Also Domain Join is going out the door as Microsofts target are Azure AD joined only endpoints (not talking about Windows Server yet). VAMT can handle activation of domain joined and non-domain joined devices. Interestingly it is not pushed in the docs. My recent PR on docs on KMS has been closed after sitting for months. Armando, can you confirm that the devices you try to activate are domain joined?Microsoft Clearinghouse server connection issues + phone line is dead end
We see a rising number of customers having issues installing or reinstalling their RDS Licenses via automatic connection. According to volume licensing support reinstalling licensing should not work this way any longer and requires customers to contact the RDS activation hotline which is +49 800 5077777 for Germany. If you dial through the menu and reach the RDS Licensing support, for weeks it is not possible to get through speaking with any agent. Instead the phone computer asks for your phone number and to enter it via your phone (DTMF). Whatever the way you enter a number like +492212343434 or 02212343434 it ends up that the voice computer says the number cannot be recognized. I guess that the Microsoft Clearinghouse server has issues with TLS 1.2 and some ciphers but we cannot pin it down even with the networking guys. Here are some possible messages: Customer A: Cannot install licenses, the server is correctly activated and can also be reactived successfully Customer B: Cannot install licenses, server ist correctly activated but can only be reactivated via web. Interestingly activating or reactivating the RDS CAL Server itself works fine on some customers On Other customers even this is not successful anymore due to connection issues. I began to see this last year when customers began to use Windows Server 2019 RDS CAL Servers, while Windows Server 2016 and 2012 R2 were unaffected. We have tried to setup a fresh Windows Server but no help. So 3 things causing a combined issue and blocker: - the RDS CAL phone support is unavailable in Germany - Automatic activation installing new licenses does not work (but is required for RDS via CSP) - Automatic activation re-installing already activated licenses does no longer work according to VL Support as - Automatic activation for Activation / Reactivation of a Server does not work anymore for some customers due to connection issues
