disk

I think we are currently leaning towards everything including Yammer. The main reason we are considering leaving Yammer is it appears as though a good number of our students and staff are already using it! I am seeing posts from before we even signed up for O365! I'm guessing this was due to Yammer being a thing before it was included with O365 subs? Just curious why those that responded chose not to roll out Yammer. Thanks!

For any of you that are using Office 365, I am curious if you wouldn't mind sharing which apps you present to your users or which you didn't want them to have access to. We are planning an on-premise exchange to Exchange Online migration and are having many discussions about what other aspects of O365 we want to offer and/or support and would love to know what some of you have done in your approach. Thanks!

MDT is definitely the way to go. SCCM can do more but is a bit more complicated. You might consider something like PDQDdeploy for installing software after imaging (not to say you can't install software during the imaging phase with MDT because you certainly can!).

Did you hear anything back from Microsoft? Also, just curious which flavor of Windows 10 you are using, Windows 10 Enterprise? 1607 build or something else?

Not sure if this link will be helpful to you or not. https://technet.microsoft.com/en-us/library/jj649079%28v=ws.11%29.aspx?f=255&MSPPError=-2147217396 I was under the impression that Microsoft was deprecating roaming profiles in favor of UE-V. I could have misread something though.

This has been a very insightful thread. I think I will have to bring this subject up again at our next meeting now that I have a bit more insight into just how it works and differs from Office 2016 VL.

Can I ask what made you decide to go with O365 Pro Plus as opposed to the regular VL Office 2016? I asked my group their opinion on the matter and didn't get much of a response. After checking out the information you linked to and some of their FAQs, etc, I'm wondering how much of a pain it will be to deploy O365 Office client to our instructional areas due to potential complications from Deep Freeze. Have you already began testing such scenarios?

I'm not 100% sure, but watching the video that xlandhenry posted above seems to indicate that it is not the case if you deploy using device activation. I've not had the time to investigate further so there are a lot of questions. For instance, do device installation licenses come from a separate pool, etc?

We have a WSUS machine group where we have approved the latest build (1607) and have assigned a number of Windows 10 Enterprise PCs running 1511. I have the following policies set and seemingly applied: Turn off auto-restart for updates during active hours: Enabled: Active Hours 7am-7pm Always automatically restart at the scheduled time: Enabled: 30 minute timer Configure Automatic Updates: Enabled: 4 - Auto download and schedule the install: Every day 01:00 Specify intranet Microsoft update service location: Enabled with location set Do not include drivers with Windows Update: Enabled Select when Feature Updates are received: Enabled: Current Branch for Business Select when Quality Updates are received: Enabled For two days now, I have checked two PCs that are running build 1511, and for two days now, when opening the Settings app and checking the Update status, one shows it has downloaded and staged build 1607 and states that 1am looks like a good time to schedule the reboot for install. That makes sense since 1am is what is set in policy. The PC was turned off when I left both days, but I verified it is waking up at midnight via the BIOS wake time. The other PC has been left on since Monday morning and has yet to download the upgrade. I have not yet had time to go through the event logs or run a diagnostic (I was thinking of trying the free SolarWinds WSUS Diag tool). That PC just shows it last installed updates on Feb 4th. Any one have any input on what may be going on here? I'm more concerned with the PC that has downloaded and staged the upgrade but refuses to actually reboot and finish installing at the specified time.

So we are just now beginning our rollout of Windows 10 and Office 2016, but one of my group brought up an interesting question. Since we have an Office 365 license for the campus, it appears as though we have the ability to push out either version of the desktop suite to our end users. Am I correct in this thinking? Are any of your institutions pushing out Office 2016 using the O365 licensing model? This was brought up due mainly to the feature updates that get rolled out on a monthly basis to Office 2016 for O365 subscribers. They worried about our users wanting/needing some of those features in the future, or at the very least, being confused as to why they have a certain feature on their home PC and not on their work PC.

Thanks for the suggestion. I was hoping to get away from using Internet Explorer. Perhaps we'll consider using Firefox instead as long as it has the appropriate kiosk functionality. It's a shame they don't allow Edge to be used with Assigned Access mode. Maybe after the Creators Update?

Thanks again for the information! I am recommending to my team to pursue that as an option.

Essentially, we have a lot of users already using Office 365 services in a variety of ways and there is a push for us to fully support them in an official manner and expand the offerings (Skype for Business, OneDrive for Business, Planner, SharePoint, Project Online, etc.). Migrating from on-premise Exchange to Exchange Online is just the first part of a larger goal for our college.

Thanks for the reply! cloudmigrator365.com was one of the products that came up while searching. It looked promising. Mind if I ask how long ago you performed your migration with their product? The reason I ask is that I've heard that recent google changes in the name of security have complicated the process. Essentially, I'm wondering if their product will allow the migration to be handled without asking the users to setup 2FA or otherwise change their settings before our Exchange/G Suite admins can perform the migration. These two links from Microsoft state the two processes that the end users would have to complete before they could be migrated, just wondering if this product circumnavigates that. https://support.office.com/en-us/article/Prepare-your-Gmail-or-G-Suite-account-for-connecting-to-Outlook-and-Office-365-b650957d-4446-425a-ab78-01b89cbead93?ui=en-US&rs=en-US&ad=US https://support.office.com/en-us/article/Enable-2-step-verification-for-your-Google-apps-users-4c70c606-5e95-4cf7-abce-cf85f1ac4179?ui=en-US&rs=en-US&ad=US

Hello all, Currently, most of our users are on on-premise exchange 2010 and a smaller portion on are google mail for education (or whatever it is currently called). Looking at this article: https://support.office.com/en-us/article/Migrate-G-Suite-mailboxes-to-Office-365-665dc56c-581c-4e35-8028-6bc1e8497016 This part is the troubling part: "Before Office 365 can connect to Gmail or G Suites, all the account owners need to create an app password to access their account." Has anyone performed this migration recently and if so, how did you approach this hurdle? We don't think this is something we can simply send out a request for those users (a few hundred) to do. Would love to know how others approached this. Optimally, we want to migrate at least the google mail users inbox to their new exchange online account.

Ok, so I know this wasn't working last time I researched this, but is anyone aware of a workaround to use Edge for kiosk use? If not, is there another Windows Store browser that anyone would recommend? I have looked through the store but they all seem to have pretty poor reviews, so I'm just wondering if any are worth trying for this purpose. Also, in general, is there any kiosk setup/management software solutions anyone would recommend? We are entertaining both free and purchased/licensed solutions. Thanks!

Did you update the adapter to the latest firmware? There may be more than one way to do so, but the easiest is to simply download and use the "Microsoft Wireless Display Adapter" app from the Windows app store.

We are leaving Edge enabled in our Windows 10 image and it is set as the default. We also provide a current version of Firefox as a secondary browser. Our users have not had any issues.

Interesting. Are you running the same image on all those different OEM PCs? We have been using Windows 10 on several different Dell OptiPlex and Latitude models for a year and have yet to experience that issue. We use the same base image for everything. It is Windows 10 Enterprise and to create our image, we use the install.wim file from media along with a sysprep answer file. We use SCCM for drivers/updates and don't bother removing any store apps or really any other image modifications (other than turning on .Net3 feature using DISM).

I read your post but there seems to be some (potentially) vital information missing. What is the make/model of PC? Which video card/driver version are you seeing this occur on? Which BIOS version?

What is the make/model of the PCs you have that are exhibiting this behavior? Are these systems running legacy BIOS or UEFI? Have you checked for an update to the BIOS?

If you see it again and don't feel like waiting, I have found the built-in Window Update Troubleshooter to work quite well. Control Panel\All Control Panel Items\Troubleshooting\All Categories\Windows Update

We haven't experienced this in any of our Windows 10 PCs yet. We are running Windows 10 Enterprise 1607 current branch. Which build are you experiencing this issue with? What hardware? BIOS up-to-date? Drivers injected and current?

Are you running Visual Studio 2015 per chance? We experienced the same error (on Windows 8.1 and 10) after deploying VS2015 through SCCM along with Windows. It appears as though it enters some files into the Default User profile (appdata->roaming) because there hasn't been another user profile created and the way the installer works. We deleted the Microsoft folder found under appdata/roaming and it fixed the Default User profile which then allowed all other users to properly sign in. That was our experience any way. *edit* The Microsoft folder that we removed to correct the sign on issue was in AppData/Local, not roaming.

Did you use the recommended tools provided by Microsoft for your Surface deployments? Perhaps you are missing some firmware update or driver? https://technet.microsoft.com/en-us/itpro/surface/microsoft-surface-deployment-accelerator