Tag: View

Cumulative Update 12 for Exchange Server 2013

Exchange team released CU12 for Exchange 2013

Issues that this cumulative update fixes:

KB 3143710 “Failed Search or Export” error occurs when an eDiscovery search in the Exchange Admin Center finishes

Microsoft Exchange Server User Monitor For Exchange 2013 and 2016

        Use the Microsoft Exchange Server User Monitor to gather real-time data to better understand current client usage patterns, and to plan for future work.
        Administrators can view details on server resource utilization as reported through server-side tracing. This tool works with Microsoft Exchange Server 2013 and 2016.
        The tool is provided as-is. At this time, there are no updates or patches planned for future release. No formal support is provided for the tool. Some minimal support may be provided by Microsoft but not all reported issues will be able to be addressed or resolved.

        Exchange Server User Monitor

      Exchange Analyzer is a great tool for every Exchange Admin

      Exchange Analyzer is a PowerShell tool that scans an Exchange Server 2013 or 2016 organization and reports on compliance with best practices.

      Exchange Analyzer is a community project, and is currently a beta release seeking feedback and results from real world environments.

      To read the latest information about Exchange Analyzer click here to visit the project’s ReadMe on Github. More information can also be found in the Exchange Analyzer Wiki.

      Installation Instructions

      1. Download the latest Zip file

      2. Extract or copy the following files and folders to a computer that has the Exchange 2013 or 2016 management shell installed. For example, place all of the files and folders in a C:\Scripts\ExchangeAnalyzer folder.

        • Run-ExchangeAnalyzer.ps1
        • \Data
        • \Modules
        • \Tests

        3. Copy the folders in the \Modules folder to C:\Windows\System32\WindowsPowerShell\v1.0\Modules\

        4. Open a new Exchange Management Shell

        Important Note: if you are updating your copy of Exchange Analyzer please make sure you copy the updated module in step 3.

        Running Exchange Analyzer

        To run the Exchange Analyzer open an Exchange management shell, navigate to the folder with the script files (e.g. C:\Scripts\ExchangeAnalyzer) and run:

        Interpreting Results

        Exchange Analyzer produces a HTML report with a simple “Passed/Failed” indicator and a list of passed and/or failed objects. Links to more info are provided to assist you with further interpretation of the report.

        Feedback and Questions

        Before submitting feedback or questions please review the Exchange Analyzer FAQ.

        You can help with bug fixes by submitting issues on Github. If you would like to contribute fixes or other code please review theExchange Analyzer Wiki.

        You can also send email to feedback@exchangeanalyzer.com.

        Change Log

        14/01/2016 – v0.1.0-Beta.1

        • First public beta release

        28/01/2016 – v0.1.1-Beta.2

        • Second beta release. Details of changes are here.

        image

        Beta Exam 345: Designing and Deploying Microsoft Exchange Server 2016 NOW AVAILABLE

        Are you an expert in designing and managing Exchange Server? Are you responsible for the Exchange Server 2016 messaging environment in an enterprise environment? If so, here’s your chance to start down the path to the MCSE certification for free AND help us improve the quality of this exam!

        We are opening up 350 beta seats for this beta exam (exam number: 70-345)… This means you can take the exam for free!! BUT… the seats are limited to first come, first served basis–so, register today (these codes will only work through February 12, 2016, meaning you have to register AND take the exam on or before that date)–and we need you take the exam as soon as possible so we can leverage your comments, feedback, and exam data in our evaluation of the quality of the questions. The sooner you take the exam, the more likely it is that we will be able to use your feedback to make improvements to the exam. This is your chance to have a voice in the questions we include on the exam when it goes live. 

        To prepare for the exam, review our prep guide and practice the skills listed: https://www.microsoft.com/en-us/learning/exam-70-345.aspx. To prepare for this beta exam, check out my recent blog for ideas: https://borntolearn.mslearn.net/b/weblog/archive/2015/12/31/just-how-does-one-prepare-for-beta-exams-without-preparation-materials.

        ***Register for the exam at the same site and use code EXCH2016010B to take it for free, but these codes are only valid for exam dates on or before Feb. 12, 2016. Remember: There are a limited amount of spots, so when they’re gone, they’re gone. You should also be aware that there are some country limitations where the beta code will not work (e.g., Turkey, Pakistan, India, China, Vietnam); you will not be able to take the beta exam for free in those countries.

        Also, keep in mind that this exam is in beta, which means that you will not be scored immediately. You will receive your final score and passing status once the exam is live.

        Well…what are you waiting for? Register before all the seats are gone!

        https://borntolearn.mslearn.net/b/weblog/archive/2016/01/13/designing-and-deploying-microsoft-exchange-server-2016-beta-exam-now-available

        Skype for Business 2015 Planning Tool

        The Skype for Business Team released Skype for Business 2015 Planning Tool. This tool asks you a series of questions about your organization and the features that you are interested in. The planning tool will then use your answers to recommend a topology based on the tested Skype for Business 2015 user model.
        Your organization may have a different user model. If so, you should adjust the recommended topology as necessary to fit your organization’s needs.
        What’s in the Planning Tool for Skype for Business 2015?

        • The Planning Tool now allow user to have up to 10 sites, including central site and disaster recovery site
        • The Planning Tool offers capacity guidance for Skype for Business Server 2015 new and updated features listed below.
        • You can answer the questions about these features in the Planning Tool, and then the suggested topology will contain information for those features, e.g hardware, network, DNS, certificate, IP, etc, according to the Skype for Business 2015 user model.
          • Persistent Chat
          • Archiving with Exchange integration
          • Mobility
          • Multi-view Video
          • SQL AlwaysOn
          • High Availability and Disaster Recovery
          • Office Web Apps
          • Exchange Mailbox
        • Skype for Business Server Planning Tool 2015 allows you to specify IPv6 IP addresses
        • Planning Tool identifies the IP conflicts across sites in the suggest topology. You can then choose to show or hide IP conflict in the topology
        • Planning Tool offers more user-friendly FQDN/IP/Port editing dialog
        • Planning Tool updates the suggested hardware requirements, DNS, and certificates with Skype for Business Server 2015 changes
        • Planning Tool updates the planning steps and deployment steps with Skype for Business Server 2015 changes
        • Planning Tool offers better support for accessibility requirements
        • Skype for Business Server Planning Tool 2015 offers improved export of Visio and Excel files. An exported Visio file matches the suggested topology diagram in the Planning Tool as well
        • Planning Tool no longer supports the following features:
          • Virtualized server design
          • Export the Planning Tool file to Topology Builder

        Get it: https://www.microsoft.com/en-us/download/details.aspx?id=50357

        Source

        Skype for Business Basic Client

        Lync Basic 2013 provides all the basic functionality that’s available in the full version of Lync (Lync 2013). However, if you want to use any of the following features, you will need to upgrade to Lync 2013:

        • Advanced call features (not available with all Office 365 subscriptions); advanced call features include team ring, call forwarding, simultaneous ring, voice mail, call park, call delegation, response groups, and remote call control
        • Calendar delegation
        • Gallery video view
        • OneNote sharing
        • Recording
        • Skill search (not available with Office 365)
        • Virtual Desktop Infrastructure (VDI) (not available with Office 365)

        Download Skype for Business Basic

        Microsoft Skype for Business Basic (64 Bit)
        http://www.microsoft.com/en-us/download/details.aspx?id=49440

        Microsoft Skype for Business Basic (32 Bit)
        http://www.microsoft.com/en-us/download/details.aspx?id=49439

        MDT 2013 Update 1 re-released (build 8298)

        MDT Team have released a newer build (8298) to address many of these issues. The Download Center is updated with the new build and is still considered MDT 2013 Update 1. Build 8290 is no longer available, no longer supported, and superseded by build 8298.

        NOTE: it can take time for the files to fully propagate through the live downloads cluster, and to be refreshed on the Akamai caches. Please ensure the build version under Details is 8298. I have seen the updated page on a non-internal system; it’s there, just be patient. Use the time to review the release notes below!

        The following issues are fixed in build 8298
        • Multiple drive partitioning issues are addressed by significant revisions to the Format and Partition Disk step (see release note below), including:
          • Upgrading to MDT 2013 Update 1 does not work for UEFI systems
          • An extra unneeded partition is created on both UEFI and BIOS systems
          • You cannot specify a custom partition layout containing a “Recovery”-type partition needed for UEFI systems
          • LTIApply error, “There is not enough space on the disk”
          • WINRE_DRIVE_SIZE from ZTIDiskpart.wsf is Too Small
        • Multiple issues related to XML processing:
          • Application bundles returning error 87
          • Selecting a keyboard locale in the Deployment Wizard
          • Deployments failing due to Unattend.xml errors
          • ZTIPatches returning error “Object required (424)”
          • Cleanup after image capture doesn’t remove LTIBootstrap entry
        • Several issues with the Windows 10 in-place upgrade task sequence including:
          • The upgrade process ends with warnings “Unable to create WebService class”
          • The upgrade task sequence is available from Windows PE
          • After upgrade a System_License_Violation blue screen appears
        • Applications that use a command file start using System32 as the working directory
        • Spanned images cannot be applied

        Below are the revised release notes and list of known issues. These inclusive lists supersede the previously published lists. New entries are marked with an asterisk (*).

        Release Notes

        TechNet documentation is not updated

        The MDT product documentation published on TechNet is current as of MDT 2013; it has not yet been updated for MDT 2013 Update 1.

        Do not upgrade from Preview to RTM

        MDT 2013 Update 1 Preview should be uninstalled before installing the final MDT 2013 Update 1. Do not attempt to upgrade a preview installation or deployment share. Although the product documentation is not updated for MDT 2013 Update 1, the information on upgrading an installation still holds true.

        Windows System Image Manager will fail to validate MDT Unattend.xml templates

        The Windows System Image Manager (WSIM, a component of the Windows ADK used to create and modify unattended installation answer files) does not allow blank values which exist in the default MDT Unattend.xml templates. When using WSIM option, Validate Answer File, it will return validation errors, such as “The ‘HorizontalResolution’ element is invalid – The value ” is invalid according to its datatype ‘HorizontalResolutionType’ – The string ” is not a valid UInt32 value.”

        MDT removes blank values before injecting the file during deployment, so Windows always receives a valid XML answer file.

        Integrating with System Center Configuration Manager

        When integrating MDT with Configuration Manager, follow the version of the Windows ADK. MDT 2013 Update 1 only works with the Windows 10 ADK, so make sure it is used with a version of Configuration Manager that supports and also uses the Windows 10 ADK.

        Image files larger than 4 GB are not split by default

        Split image (.SWM) support is now off by default. It must be enabled by modifying %DeployRoot%\Control\Settings.xml with the following:

        <SkipWimSplit>False</SkipWimSplit>

        Using HideShell with Windows 10

        The behavior of the HideShell option changed with Windows 10. Michael Niehaus explains this in great detail on his blog.

        Changes to the Format and Partition Disk step *

        The Format and Partition Disk step in the task sequence is now more closely aligned with the similar step in Configuration Manager; it will explicitly show all of the partitions that are created when the task sequence runs.

        • Backwards compatibility remains when using a task sequence that was created in a prior version of MDT. You should expect the same behavior as previously.
        • The DoNotCreateExtraPartition variable is deprecated. It should not be used with new task sequences (as the partitions are explicitly created by the task sequence step).
        Changes to permissions of new deployment shares *

        New deployment shares will now be created with more restrictive permissions. You should review these permissions and adjust accordingly for your access requirements.

        Upgraded deployment shares are not modified, but the former default permissions are overly permissive. You should review the permissions on the share and directory and adjust accordingly for your environment.

        MDT Known Issues

        Static IP not restored when using media deployment

        When doing a media deployment and using a static IP the static IP does not get restored.

        Workarounds:

        • Modify Litetouch.wsf to enable MEDIA deployments (Keith Garner explains in this forum post)
          or
        • Add an extra Apply Network Settings action (alternative suggested by Johan Arwidmark on his blog)
        Static IP not set in Network Adapter Configuration Wizard

        When initializing a deployment in Windows PE and clicking Configure Static IP Address, if you uncheck Enable DHCP and enter static IP information, the following Network Settings Error will display:

        WMI Function: Adapter.EnableStatic(IPAddress,SubnetMask) FAILURE: -2147467259

        This warning may also be seen in the results screen and log files during a deployment.

        Workaround: a static IP can be manually set from Windows PE using netsh, but otherwise there are no workarounds at this time.

        UDI wizard does not handle the domain join account user name *

        When using the OSDJoinAccount variable in CustomSettings.ini for a UDI task sequence, the wizard cannot be completed because the domain join account user name is encoded. The New Computer Details page will display an error, “User name format is invalid. Example is domain\user.”

        Workarounds:

        • Specify the OSDJoinAccount variable in the task sequence before the UDI wizard starts.
        • Alternatively, require the user to manually specify credentials in the UDI wizard.
        Unable to browse for user data path *

        In the LTI Deployment Wizard, on the User Data page, when selecting the Browse button, the Browse for Folder window does not display anything for selecting a path.

        Workarounds:

        • Manually enter the path (do not browse).
        • Set the UserDataLocation variable in CustomSettings.ini.
        The ZTIWinRE.wsf script and PrepareWinRE variable do not function properly *

        If you specify PrepareWinRE=YES in CustomSettings.ini, Windows RE does not get enabled because the commandline is malformed.

        The ZTIWinRE.wsf script is deprecated and should not be used.

        Windows 10 language packs may not install *

        We are still investigating an issue where Windows 10 language packs may not install during LTI.

        Issues after successful Windows 10 in-place upgrade *

        Following a successful upgrade to Windows 10:

        • Monitoring will continue to show the task sequence in progress until a user logs on.
        • A low rights user may receive an error at logon. This is a non-fatal error; the MDT script requires administrator elevation in order to display the final summary screen. Avoid this by using the variable, SkipFinalSummary.

        Windows 10 Known Issues

        The following are issues that are known to the MDT product team when doing Windows 10 deployments.

        Issues with CopyProfile *

        We are aware of reports of issues regarding the CopyProfile property in Unattend.xml. We have not been able to reproduce this issue, and are working with the Windows team to investigate further. If you have a reproducible issue with CopyProfile, please open a case with Microsoft Support to troubleshoot.

        USMT LoadState fails on Windows 7 *

        Using MDT 2013 Update 1 to deploy Windows 7 to an existing machine (refresh scenario), and using USMT 10 to capture and restore the user data will result in an error (“DismApi.DLL is missing”) while restoring the user state on Windows 7. This is a known issue with loadstate; see https://support.microsoft.com/kb/3084782 for more information.

        MDAC component fails being added to Windows PE

        This is a known bug with DISM; it is external to MDT. DISM can sometimes fail to add the MDAC component to WinPE boot images. This seems to be a timing issue which most commonly occur when you are using SSD disks.

        Workarounds:

        • Remove MDAC. On the deployment share properties, Windows PE tab, Features subtab, uncheck Microsoft Data Access Components (MDAC/ADO) support.
        • If you need MDAC for database connectivity, you can try updating your boot images from a system where the %TMP% directory is located on a non-SSD drive. This is not a guaranteed workaround, but has been seen to work

        NOTE: we are also aware of reports of issues regarding the WMI component in Windows PE. We have not been able to reproduce this issue, and are working with the Windows team to investigate further. If you have a reproducible issue with Windows PE optional components, please open a case with Microsoft Support to troubleshoot.

        Issues with Windows PowerShell in Windows PE

        Windows PowerShell cmdlets in Windows PE may not function as expected. We are investigating this issue with the Windows team. If you have a reproducible issue with Windows PE optional components, please open a case with Microsoft Support to troubleshoot.

        Install Exchange 2016 Prerequisites with Install-Exchange2016MailboxPrerequisites.ps1

        This script will install the needed prerequisites for the Mailbox Role of Exchange 2016 “Preview” on Server 2012 R2 .

        It will install the following:
        – Windows Componets
        – .NET Framework 4.5.2
        – Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit

        You can download the script here:
        https://gallery.technet.microsoft.com/scriptcenter/Exchange-2016-prerequisites-9a0b5e17

        MDT 2013 Update 1 Release Notes and Known Issues

        This post is to serve as the release notes and known issues list for the current release of MDT 2013 Update 1 (v6.3.8290). Source: http://blogs.technet.com/b/msdeployment/archive/2015/08/25/mdt-2013-update-1-release-notes-and-known-issues.aspx

        The list of known issues below provides a number of workarounds that are currently available to help unblock affected customers. We will revise the list as needed. Given the number of issues with this build we will release a newer build of MDT 2013 Update 1 in the next several weeks to address as many of these issues as we can. Watch this blog for more information.

        Release Notes

        TechNet documentation is not updated

        The MDT product documentation published on TechNet is current as of MDT 2013; it has not yet been updated for MDT 2013 Update 1.

        Do not upgrade from Preview to RTM

        MDT 2013 Update 1 Preview should be uninstalled before installing the final MDT 2013 Update 1. Do not attempt to upgrade a preview installation or deployment share. Although the product documentation is not updated for MDT 2013 Update 1, the information on upgrading an installation still holds true.

        Windows System Image Manager will fail to validate MDT Unattend.xml templates

        The Windows System Image Manager (WSIM, a component of the Windows ADK used to create and modify unattended installation answer files) does not allow blank values which exist in the default MDT Unattend.xml templates. MDT removes blank values before injecting the file during deployment, so Windows always receives a valid XML answer file.

        Integrating with System Center Configuration Manager

        When integrating MDT with Configuration Manager, follow the version of the Windows ADK. MDT 2013 Update 1 only works with the Windows 10 ADK, so make sure it is used with a version of Configuration Manager that supports and also uses the Windows 10 ADK.

        Image files larger than 4 GB are not split by default

        Split image (.SWM) support is now off by default. It must be enabled by modifying %DeployRoot%\Control\Settings.xml with the following:

        <SkipWimSplit>False</SkipWimSplit>

        Using HideShell with Windows 10

        The behavior of the HideShell option changed with Windows 10. Michael Niehaus explains this in great detail on his blog.

        Known Issues

        Disk partitioning issues

        Symptoms:

        • Recovery partition consumes the majority of the disk on BIOS systems
          • LTIApply fails with DISM error 112, There is not enough space on the disk.
        • Recovery partition is unnecessarily visible on both UEFI and BIOS systems
        • You can’t specify a custom partition layout containing a recovery partition for UEFI systems

        Workarounds: Keith Garner provides some suggestions on his blog: uberbug06 and uberbug07.

        Static IP not restored when using media deployment

        When doing a media deployment and using a static IP the static IP does not get restored.

        Workarounds:

        • Modify Litetouch.wsf to enable MEDIA deployments (Keith Garner explains in this forum post)
          or
        • Add an extra Apply Network Settings action (alternative suggested by Johan Arwidmark on his blog)
        Static IP not set in Network Adapter Configuration Wizard

        When initializing a deployment in Windows PE and clicking Configure Static IP Address, if you uncheck Enable DHCP and enter static IP information, the following Network Settings Error will display:

        WMI Function: Adapter.EnableStatic(IPAddress,SubnetMask) FAILURE: -2147467259

        This warning may also be seen in the results screen and log files during a deployment.

        Workaround: a static IP can be manually set from Windows PE using netsh, but otherwise there are no workarounds at this time.

        Monitoring does not work after Windows 10 upgrade

        After successfully upgrading a system to Windows 10 the MDT monitoring fails to report information. You will see the following warnings:

        Unable to create WebService class

        Workaround: None.

        MDAC component fails being added to Windows PE

        This is a known bug with DISM; it is external to MDT. DISM can sometimes fail to add the MDAC component to WinPE boot images. This seems to be a timing issue which most commonly occur when you are using SSD disks.

        Workarounds:

        • Remove MDAC. On the deployment share properties, Windows PE tab, Features subtab, uncheck Microsoft Data Access Components (MDAC/ADO) support.
        • If you need MDAC for database connectivity, you can try updating your boot images from a system where the %TMP% directory is located on a non-SSD drive. This is not a guaranteed workaround, but has been seen to work.

        NOTE: we are also aware of reports of similar issues regarding Windows PowerShell and WMI components in Windows PE (as well as some functional issues with these components). We have not been able to reproduce these issues, and are working with the Windows team to investigate further. If you have a reproducible issue with these components in Windows PE, please open a case with Microsoft Support to troubleshoot.

        Upgrade task sequences are displayed when not applicable

        Windows 10 upgrade task sequences are available when starting a deployment from Windows PE or on a non-matching architecture, however the in-place upgrade scenario is only supported when started from the full OS (it cannot be started from Windows PE) and from the correct architecture.

        Workaround: Modify your upgrade task sequence properties to exclude client platforms that are not applicable. On the task sequence properties, General tab, select This can run only on the specified client platforms and then choose platforms that you want to target, for example, All x86 Windows 7 Client. This example will exclude Windows PE and Windows 7 x64 systems.

        Applications with a command file (.cmd) use a Windows system working directory

        If you have an application that uses a command file (.cmd) as the installation command line it will be launched from C:\Windows\System32 instead of the application’s working directory.

        Workaround: See the associated bug on Connect for sample edits to ZTIApplications.wsf.

        Application bundles successfully install but log an error

        Application bundles will successfully install but the following warning is logged in ZTIApplications.log:

        SelectSingleNodeString(CommandLine) Missing Node.

        as well as the following error:

        Application <app bundle name> returned an unexpected return code: 87

        Workaround: See the associated bug on Connect for sample edits to ZTIApplications.wsf.

        Deployment Wizard error for Keyboard Locale

        Changing the keyboard locale in the Deployment Wizard will result in a script error:

        Type mismatch: 'SetNewKeyboardLayout'

        This error is non-fatal. Click Yes and continue.

        Workarounds:

        • Specify the keyboard locale in CustomSettings.ini and hide this wizard page.
        • Edit %DeployRoot%\Scripts\DeployWiz_LanguageUI.xml to remove onchange="SetNewKeyboardLayout" from line 62.
        ZTI: Offline installation of language packs or software updates fails

        Using the “Install Language Packs Offline” or “Install Updates Offline” step in an MDT-integrated task sequence in Configuration Manager results in the language packs or updates not injected, and the following errors in the ZTIPatches.log:

        ZTI ERROR - Unhandled error returned by ZTIPatches: Object required (424)

        This error is only seen in logs, the deployment appears to be successful otherwise.

        Workaround: apply updates and language packs online

        Split image files do not apply

        If you split a large image file to create .SWM file(s), then applying this split image file will fail.

        Workaround: edit %DeployRoot%\Scripts\LTIApply.wsf, both lines 915 and 918, to add a colon and remove a space, for example on line 915 change:

        sCmd = sCmd & " /SWMFile """ & sRWMPath & """"
        to
        sCmd = sCmd & " /SWMFile:""" & sRWMPath & """"

        Do the same on line 918.

        Deployment fails due to unattend.xml errors during oobeSystem

        If you have edited unattend.xml and then start a deployment with the wizard page for administrator password enabled, or specified AdminPassword in CustomSettings.ini, the deployment will fail during Windows OOBE:

        Windows could not parse or process Unattend answer file [C:\Windows\Panther\unattend.xml\ for pass [oobeSystem]. The settings specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows=Shell-Setup].

        Workaround: edit %DeployoRoot%\Scripts\ZTIConfigure.wsf lines 343 and 344 to append unattend: before PlainText. For example, on line 344 change:

        oCurrent.parentNode.selectSingleNode("PlainText").text = "true"
        to
        oCurrent.parentNode.selectSingleNode("unattend:PlainText").text = "true"

        Do the same on line 343.

        ZTI: LTIBootstrap.vbs script not found

        Towards the end of a MDT-integrated task sequence deployment in Configuration Manager a Windows Script Host popup will appear with a message similar to the following:

        Can not find script file "C:\LTIBootstrap.vbs".

        (The drive letter may be different depending upon the specific scenario.)

        Workaround: Script changes are possible but difficult and challenging. Johan Arwidmark provides an option on his blog (see Issue #2).

        LTI: Cleanup is not complete after image capture

        After capturing an image and rebooting back to the drive, autologon is still configured and an error will appear about LTIBootstrap is not found. This is a minor, non-fatal error that does not affect the captured image.

        Workaround: Script changes are possible but difficult and challenging, especially given the minor severity of the issue.

        DISM returns error 87 when applying image

        A deployment fails with the following error from DISM:

        Error: 87 (The parameter is incorrect)

        With further detail in the dism.log:

        Failed to get the filename extension of the image file

        Workarounds: This is seen when the server name is only two characters, for example DC, such that the /ImageFile parameter is similar to the following:

        "\\dc\DeploymentShare$\Operating Systems\Windows 10 Enterprise x64\sources\install.wim"

        Use a deployment share on a server whose name is three or more characters.

        If you must use a server with a two-character name, specify its fully qualified domain name in bootstrap.ini, for example

        DeployRoot=\\DC.contoso.com\DeploymentShare$

        Recertify MCSE: Messaging certification through MVA

        You’ve proven yourself. As a Microsoft Certified Solutions Expert (MCSE), you passed a rigorous series of exams to earn your certification. But, as the pace of changing technology accelerates, so does the challenge of keeping your skills up to date.

        Now, you have a convenient way to get recertified. Through Microsoft Virtual Academy, you can recertify your MCSE certification by reviewing a prescribed set of skills and passing all related assessments—on your own schedule.

        Note Not all MCSE certifications can be recertified through Microsoft Virtual Academy at this time.

        To renew your MCSE certification through Microsoft Virtual Academy:

        1. Find the skills path for your expiring certification, listed in the sections that follow.

        2. Pass all of the module-level assessments for each of the Microsoft Virtual Academy courses in the path.

          When you have completed Step 2, submit your Microsoft Virtual Academy user name and Microsoft Certification ID (MC ID) to certquest@microsoft.com.

        Your MCP transcript will reflect the new skills and expiration date for your MCSE after Microsoft has verified that you have passed all assessments.

        Please note that recertification skills paths might evolve over time. If you have already recertified, you are not responsible for taking the assessments on the new content until your next recertification cycle. However, for your own development, you may want to review those new skills at an earlier point in time.

        Recertification paths for additional MCSE and Microsoft Certified Solutions Developer (MCSD) certifications will be made available through Microsoft Virtual Academy in the coming months.

        Recertify an MCSE: Messaging certification

        Recertify with Microsoft Virtual Academy

        Finding some time now Knipogende emoticon

        Translate »