Tag: Script

Configure your Exchange 2013 server with Configure-Echange2013.ps1 Updated to V3.2

Updated to V3.2

Change List:

# V1.0 Begin
# V1.1 Added Some New Options 12-10-2014
# V1.2 Added Hyper-V Best Practise & NTFS Partition Offset
# V1.3 Added KB2995145 .NET Framework 4.5 garbage collector heap Fix
# V1.4 Added Set Minimum Disk Space Warning level (180GB Default CU6 200GB CU5)
# V1.5 Added Some new features
# V1.6 Changed the Layout & Add Move Arbitration Mailbox
# V1.7 Added PST Export & KB2990117
# V1.8 Added Full backup, Database in GB and Mailbox Size in GB Export CSV
# V1.9 Added Outlook AnyWhere & SafetyNetHoldTime
# V2.0 Added Check DatacenterActivationMode, Get-DatabaseAvailabilityGroupNetwork, Add Static Route, Disable Replation Network on DAG, Database Copies Per Volume (AutoReseed)
# V2.1 Added Edge Subscription
# V2.2 Added Check Transaction Log Growth
# V2.3 Changed the Menu to Submenu’s
# V2.4 Added Check Database White Space
# V2.5 Added MAPI HTTP External URL
# V2.6 Fixed OWA Virtual URL & HTTP URL
# V2.7 Added Fixes & Mountpoints & Changed Set Minimum Disk Space Warning Level from REG to GlobalOverride
# V2.8 Maintaince Added
# V2.9 Set Power to Highperformance
# V3.0 Check of Microsoft.Exchange.Management.PowerShell.SnapIn is loaded
# V3.1 Added Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:*.domain.com & Set-OutlookProvider -Identity EXCH -CertPrincipalName msstd:*.domain.com
# V3.2 VMware Best Practises & Fixed soms things

Download: https://gallery.technet.microsoft.com/scriptcenter/Configure-Exchange-2013-e0ffb2a6

MDT 2013 Update 2 Automatically move computers to the right OU.

On December 2010 i wrote an article: automatically move computers to the right OU.
In MDT 2012 update 1 this was an issue: MDT 2012 settings per task sequence

In MDT 2013 Update 2 this is still a issue:

How to fix:

I changed DeployWiz_SelectTS.vbs file and it work again Glimlach

1. Edit DeployWiz_SelectTS.vbs
2. Add after “Dim sTemplate”
Dim sCmd
Set Oshell = createObject(“Wscript.shell”)
3. Add before “End Function” (bottom of page)
sCmd = “wscript.exe “”” & oUtility.ScriptDir & “\ZTIGather.wsf”””
oItem = oSHell.Run(sCmd, , true)

Download DeployWiz_SelectTSMDT2013Update2.7z

Don’t forget to change every TaskSequence

clip_image002

Setup MDT 2013 (Update 2) to encrypt Windows 10 devices (Laptops) automaticlly

This  will show you how to configure your environment for BitLocker, the disk volume encryption built into Windows 10 Enterprise and Windows 10 Pro, using MDT. BitLocker in Windows 10 has two requirements in regard to an operating system deployment:

  • A protector, which can either be stored in the Trusted Platform Module (TPM) chip, or stored as a password.
  • To configure your environment for BitLocker, you will need to do the following:
  1. Configure Active Directory for BitLocker.
  2. Download the various BitLocker scripts and tools.
  3. Configure the rules (CustomSettings.ini) for BitLocker.

Configure Active Directory for BitLocker

To enable BitLocker to store the recovery key and TPM information in Active Directory, you need to create a Group Policy for it in Active Directory. For this section, we are running Windows Server 2012 R2, so you do not need to extend the Schema. You do, however, need to set the appropriate permissions in Active Directory.

Note
Depending on the Active Directory Schema version, you might need to update the Schema before you can store BitLocker information in Active Directory.

In Windows Server 2012 R2 (as well as in Windows Server 2008 R2 and Windows Server 2012), you have access to the BitLocker Drive Encryption Administration Utilities features, which will help you manage BitLocker. When you install the features, the BitLocker Active Directory Recovery Password Viewer is included, and it extends Active Directory Users and Computers with BitLocker Recovery information.

figure 2

Figure 2. The BitLocker Recovery information on a computer object in the contoso.com domain.

Add the BitLocker Drive Encryption Administration Utilities

The BitLocker Drive Encryption Administration Utilities are added as features via Server Manager (or Windows PowerShell):

  1. On DC01, log on as CONTOSO\Administrator, and, using Server Manager, click Add roles and features.
  2. On the Before you begin page, click Next.
  3. On the Select installation type page, select Role-based or feature-based installation, and click Next.
  4. On the Select destination server page, select DC01.contoso.com and click Next.
  5. On the Select server roles page, click Next.
  6. On the Select features page, expand Remote Server Administration Tools, expand Feature Administration Tools, select the following features, and then click Next:
    1. BitLocker Drive Encryption Administration Utilities
    2. BitLocker Drive Encryption Tools
    3. BitLocker Recovery Password Viewer
  7. On the Confirm installation selections page, click Install and then click Close.

figure 3

Figure 3. Selecting the BitLocker Drive Encryption Administration Utilities.

Create the BitLocker Group Policy

Following these steps, you enable the backup of BitLocker and TPM recovery information to Active Directory. You also enable the policy for the TPM validation profile.

  1. On DC01, using Group Policy Management, right-click the Contoso organizational unit (OU), and select Create a GPO in this domain, and Link it here.
  2. Assign the name BitLocker Policy to the new Group Policy.
  3. Expand the Contoso OU, right-click the BitLocker Policy, and select Edit. Configure the following policy settings:

    Computer Configuration / Policies / Administrative Templates / Windows Components / BitLocker Drive Encryption / Operating System Drives

    1. Enable the Choose how BitLocker-protected operating system drives can be recovered policy, and configure the following settings:
      1. Allow data recovery agent (default)
      2. Save BitLocker recovery information to Active Directory Domain Services (default)
      3. Do not enable BitLocker until recovery information is stored in AD DS for operating system drives (Do Not Enable This Winking smile)
    2. Enable the Configure TPM platform validation profile for BIOS-based firmware configurations policy.
    3. Enable the Configure TPM platform validation profile for native UEFI firmware configurations policy.

      Computer Configuration / Policies / Administrative Templates / System / Trusted Platform Module Services

    4. Enable the Turn on TPM backup to Active Directory Domain Services policy.

(Don’t forget to disable Secure Boot & Enable the secure boot again after deployment is succes vol!!)

Set permissions in Active Directory for BitLocker

In addition to the Group Policy created previously, you need to configure permissions in Active Directory to be able to store the TPM recovery information. In these steps, we assume you have downloaded the Add-TPMSelfWriteACE.vbs script from Microsoft to C:\Setup\Scripts on DC01.

  1. On DC01, start an elevated PowerShell prompt (run as Administrator).
  2. Configure the permissions by running the following command: 
    cscript C:\Setup\Scripts\Add-TPMSelfWriteACE.vbs

figure 4

Figure 4. Running the Add-TPMSelfWriteACE.vbs script on DC01.

Add BIOS configuration tools from Dell, HP, and Lenovo

If you want to automate enabling the TPM chip as part of the deployment process, you need to download the vendor tools and add them to your task sequences, either directly or in a script wrapper.

Add tools from Dell

The Dell tools are available via the Dell Client Configuration Toolkit (CCTK). The executable file from Dell is named cctk.exe. Here is a sample command to enable TPM and set a BIOS password using the cctk.exe tool:

cctk.exe --tpm=on --valsetuppwd=Password1234
Add tools from HP

The HP tools are part of HP System Software Manager. The executable file from HP is named BiosConfigUtility.exe. This utility uses a configuration file for the BIOS settings. Here is a sample command to enable TPM and set a BIOS password using the BiosConfigUtility.exe tool:

BIOSConfigUtility.EXE /SetConfig:TPMEnable.REPSET /NewAdminPassword:Password1234

And the sample content of the TPMEnable.REPSET file:

English
Activate Embedded Security On Next Boot
*Enable
Embedded Security Activation Policy
*No prompts
F1 to Boot
Allow user to reject
Embedded Security Device Availability
*Available
Add tools from Lenovo

The Lenovo tools are a set of VBScripts available as part of the Lenovo BIOS Setup using Windows Management Instrumentation Deployment Guide. Lenovo also provides a separate download of the scripts. Here is a sample command to enable TPM using the Lenovo tools:

cscript.exe SetConfig.vbs SecurityChip Active

CustomSettings.ini

[Default]
SkipBitLocker=YES

[LAPTOP]
TaskSequenceID=LAPTOP
MachineObjectOU=OU=Bitlocker,OU=LAPTOPS,OU=Clients,DC=wardvissers,DC=local
BDEKeyLocation=\\mdt01.wardvissers.local\Bitlocker$

Source

Cumulative Update 1 for Exchange Server 2016

Exchange Team released:  Cumulative Update 1 for Exchange Server 2016

Issues that the cumulative update fixes

KB 3139730 Edge Transport service crashes when you view the properties of a poison message in Exchange Server 2016
KB 3135689 A custom SAP ODI URI is removed by ActiveSync from an email message in an Exchange Server environment
KB 3135688 Preserves the web.config file for Outlook Web App when you apply a cumulative update in Exchange Server 2016
KB 3135601 Cyrillic characters are displayed as question marks when you run the “Export-PublicFolderStatistics.ps1” script in an Exchange Server 2016 environment
KB 3124242 Mailbox quota is not validated during migration to Exchange Server 2013 or Exchange Server 2016

Exchange Server 2016 Cumulative Update 1 (KB3134844), Download, UM Lang Packs

Don’t use DHCP Option 60/66/67 when you want to use UEFI & Legacy PXE Boot with MDT

If you want to use EUFI Boot with MDT 2013 Update X.
Don’t use DHCP Option 60/66/67!!!

DC01 = Windows Server 2008 R2 SP1
DC02 = Windows Server 2012
MDT01 = Windows Server 2012 R2

UEFI Client: Dell Laptop E5450
BIOS Client: HyperV Virtual machine with Legacy network adapert

DC1; MDT01 and DHCPServer all in Subnet1.
(IP Helper is set for DHCPServer for DHCP and for DC01 & MDT01 for DHCP and BootP – I checked serveral times if everything is right here)
UEFI Client and BIOS Client in Subnet2.

Situation1 — Using no DHCP Options and WDS running (IP HELPER-ADDRESS):
UEFI Client – Boots perfectly (contacting Server MDT01)
BIOS Client – Boots perfectly (contacting Server MDT01)

Situaion2 — Using no DHCP Options and WDS just running on MDT01:
UEFI Client – Does not boot (no error information is provided)
BIOS Client – Does not boot (no Bootfilename recieved)

Situation3 — Using DHCP Options(Option 66=”IP of MDT01″ Option 67=”\x86\wdsnbp.com”) and WDS just running on MDT01:
UEFI Client – Does not boot (no error information is provided)
BIOS Client – Boots perfectly (contacting Server DP1)

Situation4 — Using DHCP Options(Option 60=”PXEClient” Option 66=”IP of MDT01″ Option 67=”\x86\wdsnbp.com”) and WDS just running on MDT01:
UEFI Client – Boots perfectly (contacting Server DP1)
BIOS Client – Does not boot (taking hours to recieve dhcp options..)

Solution:

On most switches you can configure ip helper-addresses. This is most time al ready configured for the use of DHCP.

Add the IP of the MDT server als ip helper-address:

Example:

interface Vlan100
description GEBRUIKERS VLAN
ip address 192.168.101.254 255.255.254.0 show
ip helper-address 192.168.25.6   (DC01)
ip helper-address 192.168.25.7   (DC02)
ip helper-address 192.168.25.30 (MDT01)
end

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

    wardvissers.nl Windows 10 mobile & desktop app

    • With Microsoft app studio you can create your on app within minuts.
      I created this within 15 minuts. Cool Open-mouthed smileOpen-mouthed smileOpen-mouthed smile

    ward app1

    ward app2

      Windows 10 Mobile

      Download package

      Windows 10 Desktop

      Download package

      How to use these packages:

      • Desktop: download the installable package, unzip it and execute the powershell script Add-AppDevPackage.ps1 and follow the instructions.
      • For Mobile: download and install the prerequisites, then download the package, tap the downloaded file and your App will be automatically installed on your device.

    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.

    Office 2013 Group Policy User Settings Recommendations

    The following table lists a number of user settings across each of the Office 2013 applications that I recommend you take a look at. This is just a small subset of the total number of settings, but includes some of the most important ones.

    The status of each setting will vary dependant on the environment. Use at your own risk.

    PRODUCT
    PATH
    SETTING
    RECOMMENDED VALUES

    Microsoft Access 2013
    Miscellaneous
    Disable the Office Start Screen for Access
    Enabled | Not Configured

    Microsoft Excel 2013
    Excel Options – Save
    Default file format
    Enabled, Excel Workbook (*.xlsx)

    Microsoft Excel 2013
    Miscellaneous
    Disable the Office Start Screen for Excel
    Enabled | Not Configured

    Microsoft Office 2013
    Global Options – Customize
    Allow roaming of all user customizations
    Enabled

    Microsoft Office 2013
    Privacy – Trust Center
    Disable Opt-in Wizard on first run
    Enabled

    Microsoft Office 2013
    Privacy – Trust Center
    Enable Customer Experirnce Improvement Program
    Disabled | Not Configured

    Microsoft Office 2013
    Privacy – Trust Center
    Automatically receive small updates to improve reliability
    Disabled | Not Configured

    Microsoft Office 2013
    Privacy – Trust Center
    Send Office Feedback
    Disabled | Not Configured

    Microsoft Office 2013
    Privacy – Trust Center
    Allow including screenshot with Office Feedback
    Disabled | Not Configured

    Microsoft Office 2013
    Subscription Activation
    Do not show ‘Manage Account’ link for subscription licenses
    Enabled | Not Configured

    Microsoft Office 2013
    Subscription Activation
    Automatically activate Office with federated organization credentials
    Disabled | Not Configured

    Microsoft Office 2013
    Services
    Disable Roaming Office User Settings
    Enabled | Not Configured

    Microsoft Office 2013
    Services – Fax
    Disable Internet Fax feature
    Enabled

    Microsoft Office 2013
    Downloading Framework Components
    Hide missing component download links
    Enabled

    Microsoft Office 2013
    Microsoft Office Picture Manager
    Disable File Types association dialog box on first launch
    Enabled

    Microsoft Office 2013
    Miscellaneous
    Show SkyDrive Sign In
    Disabled | Not Configured

    Microsoft Office 2013
    Miscellaneous
    Block signing into Office
    Enabled | Not Configured

    Microsoft Office 2013
    Miscellaneous
    Disable the Office Start screen for all Office applications
    Enabled | Not Configured

    Microsoft Office 2013
    Miscellaneous
    Disable Office Backgrounds
    Enabled | Not Configured

    Microsoft Office 2013
    Miscellaneous
    Suppress recommended settings dialog
    Enabled

    Microsoft Office 2013
    First Run
    Disable First Run Movie
    Enabled | Not Configured

    Microsoft Office 2013
    First Run
    Disable First Run on application boot
    Enabled | Not Configured

    Microsoft OneNote 2013
    OneNote Options – Other
    Add OneNote icon to the notification area
    Disabled | Not Configured

    Microsoft Outlook 2013
    Outlook Social Connector
    Turn off Outlook Social Connector
    Enabled | Not Configured

    Microsoft Outlook 2013
    Outlook Social Connector
    Do not show social network info-bars
    Enabled | Not Configured

    Microsoft Outlook 2013
    Outlook Options – Preferences – Calendar Options – Office.com Sharing Service
    Prevent publishing to Office.com
    Enabled | Not Configured

    Microsoft Outlook 2013
    Outlook Options – Other – AutoArchive
    AutoArchive Settings
    Disabled

    Microsoft PowerPoint 2013
    PowerPoint Options – Save
    Default file format
    Enabled, PowerPoint Presentation (*.pptx)

    Microsoft PowerPoint 2013
    Miscellaneous
    Disable the Office Start Screen for PowerPoint
    Enabled | Not Configured

    Microsoft Project 2013
    Miscellaneous
    Disable the Office Start Screen for Project
    Enabled | Not Configured

    Microsoft Publisher 2013
    Miscellaneous
    Disable the Office Start Screen for Publisher
    Enabled | Not Configured

    Microsoft Visio 2013
    Visio Options – Save – Save Documents
    Save Visio files as
    Enabled, Visio Document

    Microsoft Visio 2013
    Visio Options – Advanced – General Options
    Put all settings in Windows registry
    Enabled

    Microsoft Word 2013
    Word Options – Save
    Default file format
    Enabled, Word Document (*.docx)

    Microsoft Word 2013
    Miscellaneous
    Disable the Office Start Screen for Word
    Enabled | Not Configured

    Translate »