Join Microsoft for four days of demos, deep dives, and live Ask Microsoft Anything (AMA) sessions from October 24-27, 2022, led by Microsoft engineering and designed to get you up to speed on the latest features, capabilities, and scenarios for Windows11 and Microsoft Intune, including Windows 365 and much more. There will be experts from the engineering and product teams ready to answer your questions during each session.
How do you participate? Go to https://aka.ms/TechnicalTakeoff and select the sessions you want to attend, and then click on RSVP to save your spot, receive event reminders, and have the ability to post your questions in advance and also during the event. (Note: You must be signed in to the Tech Community to RSVP and participate in the live Q&A, but sessions can be viewed without signing in). See the video below for a quick tutorial on how to sign up.
The tweet below has been liked, shared, and retweeted by IT pros with lots of excitement for this awesome event. Follow me on Twitter and help amplify this message. Thanks.
See below for a listing of the deep dive sessions, demos, AMAs, and the Office Hours.
All times below listed for Pacific Daylight Time (PDT)
As of Sunday, October 23, 2022, we have added a Microsoft Edge AMA on Wednesday, October 26th at 12PM PT. Check it out: https://aka.ms/TTAMA/MicrosoftEdge.
I’m excited for this event which a handful of us at Microsoft helped organize, planned and produced this amazing technical event for IT pros. Looking forward to seeing you at Microsoft Technical event, for you learning, and engagements.
The time has come to let the ?? out of the bag and make the formal announcement. On May 21, 2021, I wrote a blog post where I mentioned that I left my 18 year career in Higher-Ed as a Senior Systems Administrator at the University of Vermont.
I am excited to announce that as of today, June 7, 2021, I have joined Microsoft as a Customer Engineer for Microsoft 365. My role covers a variety of solutions under the Microsoft 365 umbrella including Modern Management which I’m very passionate and super excited about. I can finally say that I’m now a “Blue Badge” and my dream of joining Microsoft has come true!
There is so much that I want to mention and perhaps, I’ll start with my family. My wife Jenny and my daughters Sabrina and Hannah have been my rock, strength, motivation, strong supporters for what I do, and they highly encouraged me to pursue my dreams and passion. Thank you!
I’ve been privileged and honored to be a Microsoft MVP since January 2017, and I have grown and learned so much since then, as well as had many amazing opportunities, from guest blogging, consulting work, product reviews, NDA opportunities with Microsoft, Subject Matter Expert (SME) on various webinars and technical user groups, speaking engagements with several conferences including Microsoft Ignite in Orlando, Microsoft Ignite The Tours in Milan, Johannesburg, and Dubai (unfortunately COVID-19 cancelled my speaking gigs in Zurich, Mumbai, Bangalore, Tel-Aviv, and Chicago), TechMentor, IT/Dev Connections, and the one close to my heart and my favorite MMS aka MMSMOA, to name a few. During this journey, I developed strong bonds, positive reputation, respect, and trust among Microsoft product groups, MVP Program leadership, fellow Microsoft MVPs, vendors, event organizers, IT Professional community, mentees, my wonderful followers, and close friends. Thank you to all of you for your support, guidance, encouragement, and friendships.
Today also marks the end of the road for my Microsoft MVP award, which is something one has to give up upon joining Microsoft as an employee. I will continue to be a valuable resource not only to the MVP Program, the leadership, but to the IT Pro community as well, and will continue to empower everyone and help improve what I can. Thank you Betsy Weber, Rochelle Sonnenberg, and Christian Talavera for allowing me to do what I do, and most importantly for all the amazing opportunities as well as for my inclusivity as one of the trusted leaders within the MVP program. Also, Thank you Cathy Moya for the same and so much more. It’s amazing that we are all colleagues now. ?????
There are a few people who I would like to mention and recognize, who have been instrumental for my next career phase with Microsoft. The offline chats, references, internal recommendations, referring to open positions, keeping me in check, pushing me harder, motivations, encouraging me to stay positive, mentorship, discreet conversations, trust, friendships, and so much more, meant a lot to me and I’m forever appreciative and grateful. I know I am going to miss mentioning someone or another, and for that I apologize in advance and please forgive me. In no particular order, Thank you very much Noel Fairclough, Rod Trent, John Deardurff, Art Hogarth, Cathy Moya, Heather Poulsen, Kerim Hanif, Kris Loranger, Joe Lurie, and last but not least Julie Andreacola.
As I celebrate this happy occasion, I’m also reminded of my brother Amarjit who passed away on this very day (June 7th) in 2015. I miss him very much, but I know he is proud of me and is watching over me from heaven. ???
With all that said, it’s time to kick start my new adventures with the company and people I love, embrace the unique opportunities, advocate and evangelize modern technologies, support the IT Pro community, and I’m ready to “empower every person and every organization to achieve more”! ??????????✔
Update sign and text on a computer keyboard button 3D illustration.
Microsoft has released fixes for 82 vulnerabilities, with 10 updates classified as Critical and 72 as Important. Here’s an updated announcement (2021-02-09) from Microsoft: Deploy Windows SSUs and LCUs together with one cumulative update –
Beginning with the February 2021 LCU, we will now publish all future cumulative updates and SSUs for Windows 10, version 2004 and above together as one cumulative monthly update to the normal release category in WSUS.
UPDATE – 2021-03-14: DYMO Label Printer fix for BSOD issues.
UPDATE – 2021-03-13: Microsoft shares temporary fix for Windows 10 printing crashes
UPDATE – 2013-03-13: Updates on Microsoft Exchange Server Vulnerabilities (CISA)
UPDATE– 2021-03-10: Windows 10 KB5000802 (March) update is crashing PCs with BSOD Windows 10 BSOD crashes include the both workstation and server versions running March 2021 cumulative updates:
KB5000802: Windows 10 2004/20H2 & Windows Server 2004/20H2
Zero-Day Vulnerabilities Fixes: 1. Internet Explorer Memory Corruption Vulnerability (CVE-2021-26411) 2. Internet Explorer Remote Code Execution Vulnerability (CVE-2021-27085) 3. Windows Win32k Elevation of Privilege Vulnerability (CVE-2021-27077) 4. Microsoft Exchange Server Remote Code Execution Vulnerability (CVE-2021-27078)
Microsoft released out-of-band security updates for the ProxyLogon vulnerability that are actively being used by threat actors worldwide to compromise Microsoft Exchange servers.
These vulnerabilities are being tracked with the following CVEs:
CVE-2021-26855 – Microsoft Exchange Server Remote Code Execution Vulnerability
CVE-2021-26857 – Microsoft Exchange Server Remote Code Execution Vulnerability
CVE-2021-26858 – Microsoft Exchange Server Remote Code Execution Vulnerability
CVE-2021-27065 – Microsoft Exchange Server Remote Code Execution Vulnerability
Microsoft has released security updates for currently supported Microsoft Exchange cumulative updates and older unsupported versions.
Microsoft has released a PowerShell script called Test-ProxyLogon.ps1 that will check for indicators of compromise (IOC) in Exchange HttpProxy logs, Exchange log files, and Windows Application event logs.
Windows 10 v2004 and Windows 10 v20H2: 5000802 Windows 10 v1909: 5000808 Windows 10 v1809: 5000822 Windows 10 v1803: 5000809
Windows Server 2019, Windows Server 2016, and Server Core installations (2019, 2016, v20H2, v2004, and v1909)
Critical
Remote Code Execution
Windows Server 2019: 5000822 Windows Server 2016: 5000803 Windows Server v2004 and Windows Server v20H2: 5000802 Windows Server v1909: 5000808
Windows 8.1, Windows Server 2012 R2, and Windows Server 2012
Critical
Remote Code Execution
Windows 8.1 and Windows Server 2012 R2 Monthly Rollup: 5000848 Windows 8.1 and Windows Server 2012 R2 Security Only: 5000853 Windows Server 2012 Monthly Rollup: 5000847 Windows Server 2012 Security Only: 5000840
With so many people working remotely, it is a good time to review guidance on deploying security updates to remote devices, such as desktops, laptops, and tablets. Here are some resources to answer questions pertaining to deploying updates to remote devices.
Below are summaries for some of the security vulnerabilities in this release. These specific vulnerabilities were selected from the larger set of vulnerabilities in the release for one or more of the following reasons: 1) We received inquiries regarding the vulnerability; 2) the vulnerability may have received attention in the trade press; or 3) the vulnerability is potentially more impactful than others in the release. Because we do not provide summaries for every vulnerability in the release, you should review the content in the Security Update Guide for information not provided in these summaries.
Notes on details in the vulnerability summaries:
Attack Vector
This metric reflects the context by which vulnerability exploitation is possible. The Base Score increases the more remote (logically, and physically) an attacker can be in order to exploit the vulnerable component.
Attack Complexity
This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability. Such conditions may require the collection of more information about the target or computational exceptions. The assessment of this metric excludes any requirements for user interaction in order to exploit the vulnerability. If a specific configuration is required for an attack to succeed, the Base metrics should be scored assuming the vulnerable component is in that configuration.
Privileges Required
This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.
User Interaction
This metric captures the requirement for a user, other than the attacker, to participate in the successful compromise the vulnerable component. This metric determines whether the vulnerability can be exploited solely at the will of the attacker, or whether a separate user (or user-initiated process) must participate in some manner.
CVE-2021-24089
HEVC Video Extensions Remote Code Execution Vulnerability
Windows Error Reporting Elevation of Privilege Vulnerability
Impact
Elevation of Privilege
Severity
Important
Publicly Disclosed?
No
Known Exploits?
No
Exploitability
Exploitation less likely
CVSS Score Metrics
Base CVSS Score: 7.8
Privileges Required: None
Confidentiality: High
Attack Vector: Local
User Interaction: Required
Integrity: High
Attack Complexity: Low
Scope: Unchanged
Availability: High
Affected Software:
Windows 10 Version 20H2, Windows 10 Version 2004, Windows 10 Version 1909, Windows Server, version 20H2, Windows Server, version 2004, and Windows Server, version 1909
Windows Hyper-V Remote Code Execution Vulnerability
Impact
Remote Code Execution
Severity
Critical
Publicly Disclosed?
No
Known Exploits?
No
Exploitability
Exploitation less likely
CVSS Score Metrics
Base CVSS Score: 9.9
Privileges Required: Low
Confidentiality: High
Attack Vector: Network
User Interaction: None
Integrity: High
Attack Complexity: Low
Scope: Changed
Availability: High
Affected Software:
Windows 10 Version 20H2, Windows 10 Version 2004, Windows 10 Version 1909, Windows Server, version 20H2, Windows Server, version 2004, and Windows Server, version 1909
Windows DNS Server Remote Code Execution Vulnerability
Impact
Remote Code Execution
Severity
Critical
Publicly Disclosed?
No
Known Exploits?
No
Exploitability
Exploitation more likely
CVSS Score Metrics
Base CVSS Score: 9.8
Privileges Required: None
Confidentiality: High
Attack Vector: Network
User Interaction: None
Integrity: High
Attack Complexity: Low
Scope: Unchanged
Availability: High
Affected Software:
Windows Server, version 20H2, Windows Server, version 2004, Windows Server, version 1909, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, and Windows Server 2012
Internet Explorer 11 on Windows 10 Version 20H2, Windows 10 Version 2004, Windows 10 Version 1909, Windows 10 Version 1809, Windows 10 Version 1803, Windows 8.1, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, and Windows Server 2012 and Microsoft Edge (EdgeHTML-based) on Windows 10 Version 20H2, Windows 10 Version 2004, Windows 10 Version 1909, Windows 10 Version 1809, Windows 10 Version 1803, Windows Server 2019, and Windows Server 2016
Microsoft has released fixes for 56 vulnerabilities, with 11 updates classified as Critical and 43 as Important. Here’s an updated announcement (2021-02-09) from Microsoft: Deploy Windows SSUs and LCUs together with one cumulative update –
Beginning with the February 2021 LCU, we will now publish all future cumulative updates and SSUs for Windows 10, version 2004 and above together as one cumulative monthly update to the normal release category in WSUS.
Microsoft has also released Intel microcode updates for Windows 10 20H2, 2004, 1909, and older versions to fix issues impacting current and previously released Windows 10 versions.
These microcode updates are offered to affected devices via Windows Update but they can also be manually downloaded directly from the Microsoft Catalog using these links:
KB4589212: Intel microcode updates for Windows 10, version 2004 and 20H2, and Windows Server, version 2004 and 20H2
KB4589211: Intel microcode updates for Windows 10, version 1903 and 1909, and Windows Server, version 1903 and 1909
KB4589208: Intel microcode updates for Windows 10, version 1809 and Windows Server 2019
KB4589206: Intel microcode updates for Windows 10, version 1803
KB4589210: Intel microcode updates for Windows 10, version 1607 and Windows Server 2016
KB4589198: Intel microcode updates for Windows 10, version 1507
On February 9, 2021, Microsoft released security updates affecting the following Microsoft products:
Windows 10 v2004 and Windows 10 v20H2: 4601319 Windows 10 v1909: 4601315 Windows 10 v1809: 4601345 Windows 10 v1803: 4601354
Windows Server 2019, Windows Server 2016, and Server Core installations (2019, 2016, v20H2, v2004, and v1909)
Critical
Remote Code Execution
Windows Server 2019: 4601345 Windows Server 2016: 4601318 Windows Server v2004 and Windows Server v20H2: 4601319 Windows Server v1909: 4601315
Windows 8.1, Windows Server 2012 R2, and Windows Server 2012
Critical
Remote Code Execution
Windows 8.1 and Windows Server 2012 R2 Monthly Rollup: 4601384 Windows 8.1 and Windows Server 2012 R2 Security Only: 4601349 Windows Server 2012 Monthly Rollup: 4601348 Windows Server 2012 Security Only: 4601357
Below are summaries for some of the security vulnerabilities in this release:
Attack Vector
This metric reflects the context by which vulnerability exploitation is possible. The Base Score increases the more remote (logically, and physically) an attacker can be in order to exploit the vulnerable component.
Attack Complexity
This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability. Such conditions may require the collection of more information about the target or computational exceptions. The assessment of this metric excludes any requirements for user interaction in order to exploit the vulnerability. If a specific configuration is required for an attack to succeed, the Base metrics should be scored assuming the vulnerable component is in that configuration.
Privileges Required
This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.
User Interaction
This metric captures the requirement for a user, other than the attacker, to participate in the successful compromise the vulnerable component. This metric determines whether the vulnerability can be exploited solely at the will of the attacker, or whether a separate user (or user-initiated process) must participate in some manner.
CVE-2021-1727
Windows Installer Elevation of Privilege Vulnerability
Windows Win32k Elevation of Privilege Vulnerability
Impact
Elevation of Privilege
Severity
Important
Publicly Disclosed?
No
Known Exploits?
Yes
Exploitability
Exploitation detected
CVSS Base Score
7.8
Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
Affected Software
Windows 10 v20H2, Windows 10 v2004, Windows 10 v1909, Windows 10 v1809, Windows 10 v1803, Windows Server v20H2, Windows Server v2004, Windows Server v1909, and Windows Server 2019
Windows DNS Server Remote Code Execution Vulnerability
Impact
Remote Code Execution
Severity
Critical
Publicly Disclosed?
No
Known Exploits?
No
Exploitability
Exploitation more likely
CVSS Base Score
9.8
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
Affected Software
Windows Server v20H2, Windows Server v2004, Windows Server v1909, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, and Windows Server 2012
Windows Console Driver Denial of Service Vulnerability
Impact
Denial of Service
Severity
Important
Publicly Disclosed?
Yes
Known Exploits?
No
Exploitability
Exploitation less likely
CVSS Base Score
5.5
Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High
Affected Software
Windows 10 v20H2, Windows 10 v2004, Windows 10 v1909, Windows 10 v1809, Windows 10 v1803, Windows Server v20H2, Windows Server v2004, Windows Server v1909, and Windows Server 2019
Microsoft SharePoint Remote Code Execution Vulnerability
Impact
Remote Code Execution
Severity
Important
Publicly Disclosed?
No
Known Exploits?
No
Exploitability
Exploitation more likely
CVSS Base Score
8.8
Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
Affected Software
Microsoft SharePoint Server 2019, Microsoft SharePoint Enterprise Server 2016, Microsoft SharePoint Foundation 2013 Service Pack 1, and Microsoft SharePoint Foundation 2010 Service Pack 2
Microsoft Excel Remote Code Execution Vulnerability
Impact
Remote Code Execution
Severity
Important
Publicly Disclosed?
No
Known Exploits?
No
Exploitability
Exploitation less likely
CVSS Base Score
7.8
Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
Affected Software
Microsoft 365 Apps for Enterprise, Excel 2016, Excel 2013, Excel 2010, Office Online Server, Office 2019, Office 2019 for Mac, and Office Web Apps Server 2013
This month’s Office security updates address bugs exposing Windows systems running vulnerable Click to Run and Microsoft Installer (.msi) based editions of Microsoft Office products to remote code execution (RCE), information disclosure, and spoofing attacks.
Microsoft rated the six RCE bugs patched in February 2021 as Important severity issues given that they could enable attackers to execute arbitrary code in the context of the currently logged-in user.
Following successful exploitation, attackers could install malicious programs, view, change, and delete data, as well as make their own admin accounts on exploited Windows devices.
I recently discovered this website, WhatIsMyTenantID.com which provides a quick and easy way to find your Microsoft Azure Tenant ID information. It’s very simple to use. Visit the website, type your domain name, and click “Find my tenant ID” to obtain the results.
On January 12, 2021 (Pacific Time), Microsoft released security updates affecting the following Microsoft products:
Product Family
Maximum Severity
Maximum Impact
Associated KB Articles and/or Support Webpages
Windows 10 v20H2, v2004, v1909, v1809, and v1803
Critical
Remote Code Execution
Windows 10 v2004 and Windows 10 v20H2: 4598242 Windows 10 v1909: 4598229 Windows 10 v1809: 4598230 Windows 10 v1803: 4598245
Windows Server 2019, Windows Server 2016, and Server Core installations (2019, 2016, v20H2, v2004, v1909)
Critical
Remote Code Execution
Windows Server 2019: 4598230 Windows Server 2016: 4598243 Windows Server v2004 and Windows Server v20H2: 4598242 Windows Server v1909: 4598229
Windows 8.1, Windows Server 2012 R2, and Windows Server 2012
Critical
Remote Code Execution
Windows 8.1 and Windows Server 2012 R2 Monthly Rollup: 4598285 Windows 8.1 and Windows Server 2012 R2 Security Only: 4598275 Windows Server 2012 Monthly Rollup: 4598278 Windows Server 2012 Security Only: 4598297
Resources for deploying updates to remote devices:
With so many people working remotely, it is a good time to review guidance on deploying security updates to remote devices, such as desktops, laptops, and tablets. Here are some resources to answer questions pertaining to deploying updates to remote devices.
Below are summaries for some of the security vulnerabilities in this release. These specific vulnerabilities were selected from the larger set of vulnerabilities in the release for one or more of the following reasons: 1) We received inquiries regarding the vulnerability; 2) the vulnerability may have received attention in the trade press; or 3) the vulnerability is potentially more impactful than others in the release. Because we do not provide summaries for every vulnerability in the release, you should review the content in the Security Update Guide for information not provided in these summaries.
Notes on details in the vulnerability summaries:
Attack Vector
This metric reflects the context by which vulnerability exploitation is possible. The Base Score increases the more remote (logically, and physically) an attacker can be in order to exploit the vulnerable component.
Attack Complexity
This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability. Such conditions may require the collection of more information about the target or computational exceptions. The assessment of this metric excludes any requirements for user interaction in order to exploit the vulnerability. If a specific configuration is required for an attack to succeed, the Base metrics should be scored assuming the vulnerable component is in that configuration.
Privileges Required
This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.
User Interaction
This metric captures the requirement for a user, other than the attacker, to participate in the successful compromise the vulnerable component. This metric determines whether the vulnerability can be exploited solely at the will of the attacker, or whether a separate user (or user-initiated process) must participate in some manner.
CVE-2021-1674
Windows Remote Desktop Protocol Core Security Feature Bypass Vulnerability
Microsoft Word Remote Code Execution Vulnerability
Impact
Remote Code Execution
Severity
Important
Publicly Disclosed?
No
Known Exploits?
No
Exploitability
Exploitation less likely
CVSS Base Score
7.8
Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
Affected Software
Microsoft Excel 365 Apps for Enterprise, Word 2010, Word 2013, Word 2016, Office 2010, Office 2019, Office 2019 for Mac, Office Online Server, Office Web Apps 2010, Office Web Apps Server 2013, Office SharePoint Enterprise Server 2013, SharePoint Enterprise Server 2016, SharePoint Server 2010, and SharePoint Server 2019
Office security updates published as part of the January 2021 Patch Tuesday address bugs exposing Windows systems running vulnerable Click to Run and Microsoft Installer (.msi)-based editions of Microsoft Office products to remote code execution (RCE) attacks.
Microsoft rated the six RCE bugs patched this month as Important severity issues since they could enable attackers to execute arbitrary code in the context of the currently logged-in user.
Further information about each of them is available within the knowledge base articles linked below.
To download the January 2021 Microsoft Office security updates, you have to click on the corresponding knowledge base article below and then scroll down to the ‘How to download and install the update‘ section.
Generally, admins setup a shared mailboxto improve collaboration between teammates and simplify email organization. This blog post explains how to use and configure Outlook shared mailbox with step-by-step instructions, as well as what to do when you face issues with the shared mailbox.
Outlook shared mailbox is a mailbox that can be accessed by multiple users in an organization. It allows teammates to coordinate and manage activities, and all the members can read and send emails from the mailbox, update shared calendars, etc.
The following are a few benefits of using Outlook shared mailboxes:
Multiple employees in an organization can share the responsibility of handling and replying to the emails of a single mailbox.
Outlook calendar and contacts information can be shared between multiple employees.
Admin can assign specific permissions to the members of shared mailbox for security and transparency.
How to Use Outlook Shared Mailboxes?
A shared mailbox automatically shows up in your Outlook profile once the Exchange admin adds you as a member of the mailbox. If you don’t see the shared mailbox, you can restart Outlook and check again.
Note: It may take a while for the shared mailbox to display in your Outlook profile.
If you don’t see the shared mailbox in your Outlook profile even after restarting Outlook, you can add it manually by following these steps:
Launch Outlook and go to File > Account Settings > Account Settings.
Open the Email tab, select your account, and then click Change.
Select More Settings > Advanced > Add.
Enter the email ID of the shared mailbox and click OK > OK.
Click Next > Finish and then close the window.
How to Send an Email from the Shared Mailbox?
Once you have successfully setup a shared mailbox, you can send emails by following these steps:
Launch Outlook and click New Email.
Click the From field at the top and select the shared mailbox email address. If you don’t see the shared email address, select Other email address and manually enter the email address. Then click OK.
Enter your message and click Send. Now, whenever you will create a new message, you will see the shared email address in the drop-down list in the From field.
How to Use Shared Calendar and Contacts?
Once admin has allowed you to use Outlook Shared Mailboxes, the shared calendar and contacts are automatically added to the appropriate lists in your Outlook profile.
To use calendar associated with the shared mailbox:
Go to Outlook and open the calendar view.
Then select the shared mailbox.
You need to know the following things about shared calendars:
When you create appointments in a shared calendar, whoever has access to the shared mailbox can see these appointments.
Members of shared mailbox can create, view, and edit appointments in the calendar.
Like in the case of shared calendar, the shared contacts are added to your My Contacts list automatically, once the admin allows you to use Outlook shared mailboxes. To access the shared contacts, follow these steps:
Launch Outlook and select People.
Under My Contacts, select the shared contacts folder.
How to Use Shared Mailbox in Outlook Web Access (OWA)?
If you want to open a shared mailbox in a web browser via OWA, you need to know how to setup a shared mailbox in your account manually. Following are the steps to setup a shared mailbox:
Sign in to your OWA account. If you are using Office 365, sign in to your account and launch Outlook.
Right-click on a folder or your mailbox in the navigation pane, and click Add shared folder.
Enter the email ID of your shared mailbox in the dialog box and click Add.
Troubleshooting Shared Mailbox Issues
Outlook stores shared mailboxes data, like other mailbox items, locally in Outlook data file (OST). Sometimes, this OST file gets damaged or becomes inaccessible due to various reasons that include network connection issues, storage device failure, virus infection, etc. The problems with OST file may make your shared folder inaccessible or lead to syncing issues with the shared folder.
In such cases, you can delete and recreate the OST file to resolve the issues. However, if you’re not able to recreate the OST file or there are locally saved items in the file, you can recover the OST file data and save it in Outlook importable PST file by using a specialized OST to PST converter software such as Stellar Converter for OST. The software can easily convert an inaccessible or orphaned OST file into PST, in a few clicks.
Conclusion
Shared mailboxes in Outlook make it easy for small teams to manage and send emails from a common email address. These mailboxes also allow you to share contacts and calendars with the members. It’s easy to use and configure Outlook shared mailbox. You can access the shared mailbox almost instantly after the admin has made you a member.
Sometimes, you face some issues with your shared mailbox. This may usually happened due to problems with the OST file. In such a case, you can recreate the OST file to resolve the issue. If this doesn’t work, you can use an OST converter tool such as Stellar Converter for OST to save your OST file data in Outlook importable PST file.
I’m so Thankful, honored, and excited to receive the confirmation email (below) from the Microsoft Most Valuable Professional (MVP) Award team confirming my award renewal for the 2020-2021 year. This is my fourth consecutive award since receiving my first one on January 1, 2017. It has been a wonderful, exciting, fun, challenging, and rewarding experience with so many positive opportunities.
The MVP award has provided me with some great opportunities in terms of my career growth, skill development, and various avenues to give back and help others in the IT Professional community. I had been invited to speak and delivered technical and soft skill sessions at conferences such as Microsoft Ignite Orlando 2019, Midwest Management Summit (MMSMOA), MMS Jazz Edition (New Orleans), and most recently covered the international circuit at Microsoft Ignite The Tour in Milan (Italy), Johannesburg (South Africa), and Dubai (UAE). I was also scheduled to deliver sessions on behalf of Microsoft at Microsoft Ignite The Tour in Zurich (Switzerland), Mumbai (India), Bangalore (India), and Tel Aviv (Israel), however these events were unfortunately cancelled due to COVID-19. I have also delivered various webinars, guest and ghost blogged, joined some technical expert panelist, reviewed technical books, tested and evaluated software, provided technical expertise, guest on podcasts, moderated technical forums, and engaged with the community both in person and online.
This is my 4th MVP Award and I am very grateful and appreciative for this honor and for the various opportunities provided to me over time. Thank you very much to each and every one of you for making me successful in my efforts as a MVP, IT Professional, and community contributor, and for providing me with the valuable resources and networking opportunities. I could not have achieved any of the above without the support and encouragement from the community, my friends in the technology industry, people I look up to as mentors, my mentees who keep me on my toes, wonderful Program Managers at Microsoft, a few industry leaders, and last but not least my loving family. Thank you!
I would like recognize and give my special Thank you to:
The installation of the ConfigMgr client on workstations and servers is pretty straight forward, and can be done manually, with Client Push, and Software Update Based client installation to name a few. However, it is not as simple when dealing with Windows VDI systems, where extra steps need to be taken to avoid duplicate ConfigMgr client GUIDs and certificates on cloned VDI systems. Below are the steps to follow.
On the master or template system:
Install the ConfigMgr client. Ensure it is properly functioning and has all the necessary components and actions.
Stop the SMS Host Service. This can be done by launching the Command Prompt (CMD) as Administrator and running the following command: net stop ccmexec
Delete the SMSCFG.ini file from the Windows folder location. In Administrator CMD, run the following command: del %WINDIR%\SMSCFG.ini
Delete the SMS Certificates. To do this, launch PowerShell as Administrator and run the following command: Remove-Item -Path HKLM:\Software\Microsoft\SystemCertificates\SMS\Certificates\* -Force
Remove the Inventory Action ID 1 in WMI. You can run the following command: wmic /namespace:\root\ccm\invagt path inventoryActionStatus where InventoryActionID=”{00000000-0000-0000-0000-000000000001}” DELETE /NOINTERACTIVE
Once the above steps have been completed, shutdown the master template, capture a snapshot, and provision the VDI systems. At this point, each VDI system will generate a unique ConfigMgr GUID and will function as expected.
For step number 5, this can be achieved by using the wbemtest tool with the following steps:
Launch wbemtest as Administrator
Click Connect
Change the Namespace field as root\ccm\invagt, and click Connect
Click on Enum Classes
Select Recursive and click Ok
Scroll down and locate InventoryActionStatus, and double click
I came across this great opportunity from Microsoft for some free Azure training and a free exam voucher for the AZ-900 certification. See below:
Join us for Microsoft Azure Training Day: Fundamentals to improve your understanding of cloud concepts and acquire the knowledge you need to earn the Microsoft Azure Fundamentals certification. Learn basic strategies for transitioning to the cloud along with concepts including security, high availability, scalability, elasticity, agility, fault tolerance, and disaster recovery.
You will find the sign up links for the free Azure training for different dates and time zones starting from end of April to end of June 2020. Keep in mind that some dates have filled to capacity. Sign Up: https://bit.ly/2VmlZFu
