O
OzzFan
Guest
Hello,
I opened a Microsoft Premier support case for this issue, had this confirmed as a bug in the product, but was told to post this here to get it fixed.
Here's the problem and scenario:
We're about 40% of the way through rolling out Windows 10 across our entire organization. We're using group policy with folder redirection into local OneDrive for Business folders as outlined here: Redirect and move Windows known folders to OneDrive
We recently came across reports from our users that they were trying to use the built-in Microsoft Print to PDF feature and couldn't get their documents created. After various bits of troubleshooting on our side and discovered that the issue is specifically with files or folder names with a comma in them, and since our OneDrive for Business Identity name contains a comma, this bug effectively prevents anyone in our company from being able to use this very handy feature.
We opened a support case initially to see what the impact would be if we changed our ODfB Identity name, and confirmed that we would have to change our Group Policy and Identity name at the same time, and create scripts to clean up the mess (orphaned OneDrive for Business folders, stopping and restarting of the OneDrive client, etc.).
Since we do not have the resources to perform all that without disruption to our business, we requested to change the case to a bug fix instead. We were told by three different Support Technicians that a bug fix was entered but declined to fix since there is a workaround available - changing identity, saving locally and moving the file, or using an alternative product. These solutions would work but they aren't really ideal and I'd think a bug should be fixed, no matter how small or critical (and this is certainly not critical). We would have even accepted that the bug fix won't make it until the 2018 version of Windows 10, so long as we had a path to upgrade and confirmation that it would be fixed.
We were also told that if we want to get this bug fixed, we needed to post our problem here in hopes that a developer would see this, replicate, confirm, and enter a bug fix. So, any chances this will get attention?
More...
I opened a Microsoft Premier support case for this issue, had this confirmed as a bug in the product, but was told to post this here to get it fixed.
Here's the problem and scenario:
We're about 40% of the way through rolling out Windows 10 across our entire organization. We're using group policy with folder redirection into local OneDrive for Business folders as outlined here: Redirect and move Windows known folders to OneDrive
We recently came across reports from our users that they were trying to use the built-in Microsoft Print to PDF feature and couldn't get their documents created. After various bits of troubleshooting on our side and discovered that the issue is specifically with files or folder names with a comma in them, and since our OneDrive for Business Identity name contains a comma, this bug effectively prevents anyone in our company from being able to use this very handy feature.
We opened a support case initially to see what the impact would be if we changed our ODfB Identity name, and confirmed that we would have to change our Group Policy and Identity name at the same time, and create scripts to clean up the mess (orphaned OneDrive for Business folders, stopping and restarting of the OneDrive client, etc.).
Since we do not have the resources to perform all that without disruption to our business, we requested to change the case to a bug fix instead. We were told by three different Support Technicians that a bug fix was entered but declined to fix since there is a workaround available - changing identity, saving locally and moving the file, or using an alternative product. These solutions would work but they aren't really ideal and I'd think a bug should be fixed, no matter how small or critical (and this is certainly not critical). We would have even accepted that the bug fix won't make it until the 2018 version of Windows 10, so long as we had a path to upgrade and confirmation that it would be fixed.
We were also told that if we want to get this bug fixed, we needed to post our problem here in hopes that a developer would see this, replicate, confirm, and enter a bug fix. So, any chances this will get attention?
More...
