diff --git a/Exchange/ExchangeOnline/public-folders/permissions-settings-not-propagate-eac.md b/Exchange/ExchangeOnline/public-folders/permissions-settings-not-propagate-eac.md index 9f54144417..f695a040c0 100644 --- a/Exchange/ExchangeOnline/public-folders/permissions-settings-not-propagate-eac.md +++ b/Exchange/ExchangeOnline/public-folders/permissions-settings-not-propagate-eac.md @@ -31,7 +31,7 @@ You try to use the Exchange admin center (EAC) to update the permissions or othe - Microsoft Exchange Online: - The EAC doesn't provide an option to apply your changes to subfolders. -The following sections provide PowerShell workarounds for multiple scenarios. +The following sections provide PowerShell workarounds for various issues. ## Permissions aren't applied to all subfolders diff --git a/Microsoft365/admin/installation/product-ids-supported-office-deployment-click-to-run.md b/Microsoft365/admin/installation/product-ids-supported-office-deployment-click-to-run.md index 3df5006d5f..1def83ff4e 100644 --- a/Microsoft365/admin/installation/product-ids-supported-office-deployment-click-to-run.md +++ b/Microsoft365/admin/installation/product-ids-supported-office-deployment-click-to-run.md @@ -3,7 +3,7 @@ title: Product IDs that are supported by the Office Deployment Tool for Click-to description: Lists product IDs that the Office Deployment Tool for Click-to-Run supports. author: helenclu ms.author: luche -ms.date: 03/31/2024 +ms.date: 12/09/2024 manager: dcscontentpm search.appverid: - MET150 @@ -62,54 +62,72 @@ In addition to these product IDs, the following non-Microsoft 365 product IDs ar - `AccessRetail` - `Access2019Retail` - `Access2021Retail` +- `Access2024Retail` - `Access2019Volume` - `Access2021Volume` +- `Access2024Volume` - `ExcelRetail` - `Excel2019Retail` - `Excel2021Retail` +- `Excel2024Retail` - `Excel2019Volume` - `Excel2021Volume` +- `Excel2024Volume` - `HomeBusinessRetail` - `HomeBusiness2019Retail` - `HomeBusiness2021Retail` +- `HomeBusiness2024Retail` - `HomeStudentRetail` - `HomeStudent2019Retail` - `HomeStudent2021Retail` +- `Home2024Retail` - `O365HomePremRetail` - `OneNoteFreeRetail` - `OneNoteRetail` - `OneNote2021Volume` +- `OneNote2024Volume` - `OutlookRetail` - `Outlook2019Retail` - `Outlook2021Retail` +- `Outlook2024Retail` - `Outlook2019Volume` - `Outlook2021Volume` +- `Outlook2024Volume` - `Personal2019Retail` - `Personal2021Retail` - `PowerPointRetail` - `PowerPoint2019Retail` - `PowerPoint2021Retail` +- `PowerPoint2024Retail` - `PowerPoint2019Volume` - `PowerPoint2021Volume` +- `PowerPoint2024Volume` - `ProfessionalRetail` - `Professional2019Retail` - `Professional2021Retail` +- `Professional2024Retail` - `ProjectProXVolume` - `ProjectPro2019Retail` - `ProjectPro2021Retail` +- `ProjectPro2024Retail` - `ProjectPro2019Volume` - `ProjectPro2021Volume` +- `ProjectPro2024Volume` - `ProjectStdRetail` - `ProjectStdXVolume` - `ProjectStd2019Retail` - `ProjectStd2021Retail` +- `ProjectStd2024Retail` - `ProjectStd2019Volume` - `ProjectStd2021Volume` +- `ProjectStd2024Volume` - `ProPlus2019Volume` - `ProPlus2021Volume` +- `ProPlus2024Volume` - `ProPlusSPLA2021Volume` - `ProPlus2019Retail` - `ProPlus2021Retail` +- `ProPlus2024Retail` - `PublisherRetail` - `Publisher2019Retail` - `Publisher2021Retail` @@ -118,22 +136,29 @@ In addition to these product IDs, the following non-Microsoft 365 product IDs ar - `Standard2019Volume` - `Standard2021Volume` - `StandardSPLA2021Volume` +- `Standard2024Volume` - `VisioProXVolume` - `VisioPro2019Retail` - `VisioPro2021Retail` +- `VisioPro2024Retail` - `VisioPro2019Volume` - `VisioPro2021Volume` +- `VisioPro2024Volume` - `VisioStdRetail` - `VisioStdXVolume` - `VisioStd2019Retail` - `VisioStd2021Retail` +- `VisioStd2024Retail` - `VisioStd2019Volume` - `VisioStd2021Volume` +- `VisioStd2024Volume` - `WordRetail` - `Word2019Retail` - `Word2021Retail` +- `Word2024Retail` - `Word2019Volume` - `Word2021Volume` +- `Word2024Volume` For managing the Lync or Skype for Business clients, the following table lists the tool version and the correct product ID. @@ -145,3 +170,4 @@ For managing the Lync or Skype for Business clients, the following table lists t |Skype for Business 2019 (volume licensed) |[Office Deployment Tool](https://go.microsoft.com/fwlink/p/?LinkID=626065) |`SkypeforBusiness2019Volume` | |Skype for Business Basic 2019 |[Office Deployment Tool](https://go.microsoft.com/fwlink/p/?LinkID=626065) |`SkypeforBusinessEntry2019Retail` | |Skype for Business LTSC 2021|[Office Deployment Tool](https://go.microsoft.com/fwlink/p/?LinkID=626065)|`SkypeforBusiness2021Volume`| +|Skype for Business LTSC 2024|[Office Deployment Tool](https://go.microsoft.com/fwlink/p/?LinkID=626065)|`SkypeforBusiness2024Volume`| diff --git a/Office/Client/clienttoc/toc.yml b/Office/Client/clienttoc/toc.yml index aedb3cbebe..ecc4855365 100644 --- a/Office/Client/clienttoc/toc.yml +++ b/Office/Client/clienttoc/toc.yml @@ -591,6 +591,10 @@ href: ../excel/vba-writes-to-cells-slowly.md - name: Wrap text doesn't adjust row height href: ../excel/wrap-text-not-adjust-row-height.md + - name: Forms + items: + - name: Resolve file upload errors in Microsoft Forms + href: ../forms/resolve-file-upload-errors-microsoft-forms.md - name: InfoPath items: - name: Disable code-behind prompt for InfoPath forms diff --git a/Office/Client/forms/resolve-file-upload-errors-microsoft-forms.md b/Office/Client/forms/resolve-file-upload-errors-microsoft-forms.md new file mode 100644 index 0000000000..e8cf399182 --- /dev/null +++ b/Office/Client/forms/resolve-file-upload-errors-microsoft-forms.md @@ -0,0 +1,214 @@ +--- +title: Resolve file upload errors in Microsoft Forms +description: Resolve some common errors that you might exprience when you try to add a file upload question to a form or upload a file. +author: helenclu +ms.reviewer: zakirh +manager: dcscontentpm +search.appverid: + - MET150 +audience: ITPro +ms.topic: troubleshooting +ms.service: forms +ms.custom: + - sap:Working with Forms\Issues that are related to form submission + - CI964 + - CSSTroubleshoot +appliesto: + - Microsoft Forms +ms.date: 12/09/2024 +--- + +# Resolve file upload errors in Microsoft Forms + +Files that are uploaded through Microsoft Forms are stored in Microsoft SharePoint or in OneDrive for work or school, as follows: + +- Files that are uploaded to group forms are stored in the document library on the Microsoft 365 group's SharePoint site. +- Files that are uploaded to individual forms are stored in the form author's personal OneDrive folder. + +When you use the file upload functionality in Forms, you might receive an error message in the following scenarios: + +- You [try to add a file upload question](https://support.microsoft.com/office/add-questions-that-allow-for-file-uploads-6a75a658-c02b-450e-b119-d068f3cba4cf) to a form. +- You try to upload a file in response to a question. + +These errors might occur if file uploads to SharePoint or OneDrive are blocked. This article lists some common error messages and the methods to fix the errors. + +## Error: We weren't able to create an upload file folder in OneDrive for Business + +This error can occur for the following reasons: + +- The **Limited-access user permission lockdown mode** site collection feature is enabled. This feature restricts sharing and access to files and folders. +- The [*People in your organization* sharing links](/microsoft-365/solutions/microsoft-365-limit-sharing?view=o365-worldwide#people-in-your-organization-sharing-links&preserve-view=true) are disabled. +- Sharing files and folders is limited to site owners. + +### Resolution + +To fix this error for an individual form that you create, sign in to your OneDrive for work or school website, and then follow these steps: + +1. Disable the **Limited-access user permission lockdown mode** site collection feature if it's enabled. + + 1. Select the **Settings** icon in the upper-right corner of the screen. + 1. Select **OneDrive settings** > **More Settings**. + 1. Under **Features and storage**, select **Site collection features**. + 1. Locate **Limited-access user permission lockdown mode**. If its **Status** value is **Active**, select **Deactivate**, and then select **Deactivate this feature** on the confirmation page. +1. Enable the *People in your organization* sharing links if they're disabled. + + **Note**: You must be a SharePoint Online administrator and a site collection administrator to run the following PowerShell commands in [SharePoint Online Management Shell](/powershell/sharepoint/sharepoint-online/connect-sharepoint-online). + + To check whether link sharing is disabled in your OneDrive site, run the following PowerShell command: + + ```powershell + (Get-SPOSite ).DisableCompanyWideSharingLinks + ``` + + If link sharing is disabled, run the following PowerShell command to enable company-wide link sharing for your OneDrive site: + + ```powershell + Set-SPOSite -Identity -DisableCompanyWideSharingLinks NotDisabled + ``` + + Typically, the URL for a personal OneDrive site is in the following format: + + `https://-my.sharepoint.com/personal/` + +To fix this error for a group form, sign in to the Microsoft 365 group's SharePoint site, and then follow these steps: + +1. Follow the steps in [Enable or disable site collection features](https://support.microsoft.com/office/enable-or-disable-site-collection-features-a2f2a5c2-093d-4897-8b7f-37f86d83df04) to disable the **Limited-access user permission lockdown mode** site collection feature is enabled if it's enabled. +1. Enable the *People in your organization* sharing links if they're disabled. + + **Note**: You must be a SharePoint Online administrator and a site collection administrator to run the following PowerShell commands in [SharePoint Online Management Shell](/powershell/sharepoint/sharepoint-online/connect-sharepoint-online). + + To check whether link sharing is disabled in the SharePoint site, run the following PowerShell command: + + ```powershell + (Get-SPOSite ).DisableCompanyWideSharingLinks + ``` + + If link sharing is disabled, run the following PowerShell command to enable company-wide link sharing for the group's SharePoint site: + + ```powershell + Set-SPOSite -Identity -DisableCompanyWideSharingLinks NotDisabled + ``` + + Typically, the URL for a Microsoft 365 group's SharePoint site is in the following format: + + `https://.sharepoint.com/sites/` + + > [!NOTE] + > If information barriers are enabled in your SharePoint site, company-wide link sharing is disabled if the [mode](/purview/information-barriers-sharepoint#sharing-sites-for-ib-modes) is set to **Owner Moderated**, **Implicit**, or **Explicit**. In this case, change the information barriers mode to **Open**. To check the information barriers mode of your site, run the `Get-SPOSite | Select InformationBarriersMode` PowerShell command. +1. Check whether site members can share files and folders. If they can't, follow these steps to update the sharing permission: + + 1. Sign in to the group's SharePoint site as a site owner. + 1. Select **Settings** > **Site permissions**. + 1. Under **Site Sharing**, select **Change how members can share**. + 1. Under **Sharing permissions**, select one of the following options: + + - Site owners and members can share files, folders, and the site. People with Edit permissions can share files and folders. + - Site owners and members, and people with Edit permissions can share files and folders, but only site owners can share the site. + 1. Select **Save**. + +## Error: Failed to upload your file + +This error occurs if the [*People in your organization* sharing links](/microsoft-365/solutions/microsoft-365-limit-sharing?view=o365-worldwide#people-in-your-organization-sharing-links&preserve-view=true) are disabled. + +To fix this error, enable the links by using the [Set-SPOSite](/powershell/module/sharepoint-online/set-sposite?view=sharepoint-ps&preserve-view=true) PowerShell command in [SharePoint Online Management Shell](/powershell/sharepoint/sharepoint-online/connect-sharepoint-online). + +**Note**: You must be a SharePoint Online administrator and a site collection administrator to run the following PowerShell commands. + +- For an individual form that you create, run the following PowerShell command: + + ```powershell + Set-SPOSite -Identity -DisableCompanyWideSharingLinks NotDisabled + ``` + + To verify the status of link sharing, run the following PowerShell command: + + ```powershell + (Get-SPOSite ).DisableCompanyWideSharingLinks + ``` + + Typically, the URL for a personal OneDrive site is in the following format: + + `https://-my.sharepoint.com/personal/` + +- For a group form, run the following PowerShell command: + + ```powershell + Set-SPOSite -Identity -DisableCompanyWideSharingLinks NotDisabled + ``` + + To verify the status of link sharing, run the following PowerShell command: + + ```powershell + (Get-SPOSite ).DisableCompanyWideSharingLinks + ``` + + Typically, the URL for a group SharePoint site is in the following format: + + `https://.sharepoint.com/sites/` + + > [!NOTE] + > If information barriers are enabled in your SharePoint site, company-wide link sharing is disabled if the [mode](/purview/information-barriers-sharepoint#sharing-sites-for-ib-modes) is set to **Owner Moderated**, **Implicit**, or **Explicit**. In this case, change the information barriers mode to **Open**. To check the information barriers mode of your site, run the `Get-SPOSite | Select InformationBarriersMode` PowerShell command. + +## Error: Access denied. You do not have permissions to perform this action or access this resource + +This issue occurs if you try to access the form by using an unmanaged device while SharePoint access is blocked for unmanaged devices. + +To fix this error, follow these steps as a SharePoint administrator: + +1. In the [SharePoint admin center](https://go.microsoft.com/fwlink/?linkid=2185219), select **Policies** > **Access control**. +1. Select **Unmanaged devices**, and then select one of the following settings: + + - Allow full access from desktop apps, mobile apps, and the web + - Allow limited, web-only access + +## Error: Uploaded file(s) is expired or broken, please upload your files again + +This error occurs if the **Require documents to be checked out before they can be edited** setting is enabled in the OneDrive or SharePoint site. + +### Resolution + +To fix this error for an individual form that you create, sign in to your OneDrive for work or school site, and then follow these steps: + +1. Select the **Settings** icon in the upper-right corner of the screen. +1. Select **OneDrive settings** > **More settings**. +1. Under **Can't find what you are look for**, select **Return to the old Site settings page**. +1. Under **Site Administration**, select **Site libraries and lists**. +1. Locate the library that stores the personal form, and then select **Customize "\"**. +1. Under **General Settings**, select **Versioning settings**. +1. Under **Require Check Out** > **Require documents to be checked out before they can be edited?**, select **No**. +1. Select **OK**. + +To fix this error for a group form, sign in to the Microsoft 365 group's SharePoint site, and then follow these steps: + +1. Select the library that stores the group form. +1. Select the **Settings** icon in the upper-right corner of the screen. +1. Select **Library settings** > **More library settings**. +1. Under **General Settings**, select **Versioning settings**. +1. Under **Require Check Out** > **Require documents to be checked out before they can be edited?**, select **No**. +1. Select **OK**. + +## Error: You do not have access to create this folder or you do not have a valid license + +This issue occurs if the New Folder command is disabled in the site settings. This would prevent you from creating folders in the document library where the form is stored. + +### Resolution + +To fix this error for an individual form that you create, sign in to your OneDrive for work or school site, and then follow these steps: + +1. Select the **Settings** icon in the upper-right corner of the screen. +1. Select **OneDrive settings** > **More settings**. +1. Under **Can't find what you are look for**, select **Return to the old Site settings page**. +1. Under **Site Administration**, select **Site libraries and lists**. +1. Locate the library that stores the personal form, and then select **Customize "\"**. +1. Under **General Settings**, select **Advanced settings**. +1. Under **Folders** > **Make "New Folder" command available**, select **Yes**. +1. Select **OK**. + +To fix this error for a group form, sign in to the Microsoft 365 group's SharePoint site and follow these steps: + +1. Select the library that stores the group form. +1. Select the **Settings** icon in the upper-right corner of the screen. +1. Select **Library settings** > **More library settings**. +1. Under **General Settings**, select **Advanced settings**. +1. Under **Folders > Make "New Folder" command available**, select **Yes**. +1. Select **OK**. diff --git a/Outlook/Client/message-body/how-tnef-affects-email-messages.md b/Outlook/Client/message-body/how-tnef-affects-email-messages.md index d4e5d914a8..a5273c80fa 100644 --- a/Outlook/Client/message-body/how-tnef-affects-email-messages.md +++ b/Outlook/Client/message-body/how-tnef-affects-email-messages.md @@ -1,5 +1,5 @@ --- -title: How message format affects email messages in Outlook +title: How Message Format Affects Email Messages description: Describes how message format and encoding, such as HTML, Rich Text, and TNEF, affect email messages. author: cloud-writer ms.author: meerak @@ -18,7 +18,7 @@ search.appverid: MET150 ms.date: 12/05/2024 --- -# How message format affects email messages in Outlook +# How message format affects email messages @@ -28,18 +28,18 @@ Microsoft Outlook can send email messages in any of the following formats: - **Plain Text**: Compatible with all email clients. However, any formatting, pictures, and links in the message are lost. -- **Rich Text**: Outlook uses Transport Neutral Encapsulation Format (TNEF) to package message information. Recipient messaging systems that aren't based on Microsoft Exchange might not be able to interpret messages that use this TNEF format. If the recipient's messaging system can't process this format, a file attachment that's named Winmail.dat is added to the message. +- **Rich Text**: Outlook uses Transport Neutral Encapsulation Format (TNEF) to package message information. Recipient messaging systems that aren't based on Microsoft Exchange might not be able to interpret messages that use this TNEF format. If the recipient's messaging system can't process this format, a file attachment that's named **Winmail.dat** is added to the message. ## TNEF details -A TNEF-encoded message contains a plain text version of the message, and a binary attachment that packages other parts of the original message. In most cases, the binary attachment is named Winmail.dat, and might include the following information: +A TNEF-encoded message contains a plain text version of the message, and a binary attachment that packages other parts of the original message. In most cases, the binary attachment is named **Winmail.dat**, and might include the following information: - The formatted text version of the message (for example, font information and colors) - OLE objects (for example, embedded pictures and embedded Microsoft Office documents) - Special Outlook features (for example, custom forms, voting buttons, and meeting requests) - Regular file attachments that were added to the original message -Additionally, the path of your personal folders (.pst) file and your sign-in name are embedded in the Winmail.dat file. Although this data isn't explicitly exposed to the recipient, if the recipient opens the Winmail.dat file in a binary or text editor, they can see the path and sign-in name. Password information isn't revealed. To make sure that the path of your .pst file and your sign-in name aren't sent, follow the recommendations in this article for how to send messages that don't include the Winmail.dat file. +Additionally, the path of your personal folders (.pst) file and your sign-in name are embedded in the **Winmail.dat** file. Although this data isn't explicitly exposed to the recipient, if the recipient opens the **Winmail.dat** file in a binary or text editor, they can see the path and sign-in name. Password information isn't revealed. To make sure that the path of your .pst file and your sign-in name aren't sent, follow the recommendations in this article for how to send messages that don't include the **Winmail.dat** file. Some Outlook features require internet email recipients that use Outlook to have TNEF encoding enabled. For example, if you send a message that has voting buttons to a recipient over the internet, the voting buttons aren't available if the recipient doesn't have TNEF enabled. TNEF isn't required for messages that have regular file attachments. If you're sending messages that have file attachments to a recipient who doesn't use Outlook or the Exchange client, we recommend that you manually choose an email format that doesn't require TNEF (such as HTML or plain text). If a message is sent without TNEF, the recipient can view and save attachments as expected. @@ -47,15 +47,15 @@ Some Outlook features require internet email recipients that use Outlook to have When an email client that doesn't support TNEF receives a message containing TNEF information, the following outcomes commonly occur: -- The plain text version of the message is received and the message has an attachment that's named Winmail.dat. The Winmail.dat attachment has no useful information when it's opened because it's in the TNEF format. +- The plain text version of the message is received and the message has an attachment that's named **Winmail.dat**. The **Winmail.dat** attachment has no useful information when it's opened because it's in the TNEF format. -- The plain text version of the message is received and the message has an attachment that has a generic name such as ATT00008.dat or ATT00005.eml. In this case, the client can't recognize either the TNEF part of the message or the Winmail.dat file name. Therefore, a file name is created to hold the TNEF information. +- The plain text version of the message is received and the message has an attachment that has a generic name such as **ATT00008.DAT** or **ATT00005.eml**. In this case, the client can't recognize either the TNEF part of the message or the **Winmail.dat** file name. Therefore, a file name is created to hold the TNEF information. Similar to how the receiving client behaves, it's common for an email server to strip out TNEF information from messages as it delivers them. If a server option to remove TNEF is enabled, clients always receive a plain text version of the message. Exchange Server is an example of an email server that can remove TNEF from messages. ### Message encoding -The internet standards for message encoding, such as Multipart Internet Mail Extensions (MIME) and UUENCODE, are independent of TNEF. TNEF can exist in a MIME-encoded message as a MIME body part of type `application/ms-tnef`, or in a UUENCODED message as an attachment that's named Winmail.dat. To correctly display the encapsulated information, the receiving client must support TNEF encoding. +The internet standards for message encoding, such as Multipart Internet Mail Extensions (MIME) and UUENCODE, are independent of TNEF. TNEF can exist in a MIME-encoded message as a MIME body part of type `application/ms-tnef`, or in a UUENCODED message as an attachment that's named **Winmail.dat**. To correctly display the encapsulated information, the receiving client must support TNEF encoding. ### Manage TNEF in messages @@ -83,7 +83,7 @@ You can manage TNEF by using any of the following methods: To disable TNEF, follow these steps: -1. Create a text file that's named _disable-tnef.reg_. +1. Create a text file that's named **disable-tnef.reg**. 2. Copy and paste the following text into the file, and then save the file: @@ -91,7 +91,7 @@ To disable TNEF, follow these steps: > [HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Preferences] > "DisableTNEF"=dword:1 -3. Double-click _disable-tnef.reg_ to run it. +3. Double-click **disable-tnef.reg** to run it. 4. When you're prompted for approval, select **Yes**. @@ -120,11 +120,11 @@ To enable TNEF, follow these steps: Use the relevant solution for each of the following issues: -- Problem: Recipient receives the Winmail.dat attachment. +- Problem: Recipient receives the **Winmail.dat** attachment. Solution: Disable TNEF (globally or per-message). -- Problem: Recipient receives the ATT00001.DAT attachment. +- Problem: Recipient receives the **ATT00001.DAT** attachment. Solution: Disable TNEF (globally or per-message).