Nebula will no longer support older versions of Internet Explorer.

What and When:

On January 12, 2016 Microsoft will drop support for older versions of Internet Explorer, leaving IE11 as the only supported version of Internet Explorer.

Following UW security guidelines, Nebula will also remove its support, because web browsers without vendor support no longer get patches for security vulnerabilities.

To implement Nebula’s change in support, Nebula will retire the mechanism it has provided to defer automatic IE version upgrades. The mechanism to defer allowed individual computers to avoid the automatic upgrade of IE version, but was available only upon request. Nebula will continue to provide the automatic update mechanism.

What you need to do:

Nebula computer has a version of IE older that version 11, then your computer will be affected, otherwise you are unaffected.

If you are affected, we encourage you to explore your alternatives. Options to pursue may include:

-try to use the latest IE version. If you’d like to remove your IE version upgrade exception before 1/11/2016, please let us know.

-try another browser. Most applications do support browsers other than IE.

-talk with the application vendor about their browser support plan given that Microsoft will no longer support older IE versions

If there’s anything else Nebula can do to assist, please feel free to contact us at help@uw.edu. We’d be happy to provide assistance on a consulting basis.

More info:

Microsoft’s announcement of this change came via the IEBlog over a year ago.

Nebula’s browser support is documented at http://www.washington.edu/itconnect/wares/nebula/operating-system-and-browser-support/.

Nebula has been hard at work getting ready for Windows 10 for many months. Since this is a popular topic of interest, here’s a status update.

Basic Readiness

If you want to deploy a computer with Windows 10 enterprise, you can do that now. Contact us if you need help with that. The most basic of our processes are ready for that, but at this time, there are significant limitations to our support capabilities (see Full Support below), so we’d suggest you hold off a month.

If you wait a month, the story will improve significantly, and if you wait a couple months, we hope to manage the upgrade for you (see Special New Capabilities below).

Looking further out, we’ll be adjusting the specific operating systems we support (see Consequences of a New Windows OS below).

We plan to have more detailed messaging about Windows 10 support in the future, covering expectations and actions to take if you are ready to upgrade.

Full Support

There are several missing support capabilities which might lead you to delay a little longer:

1. We do not yet have a Windows 10 image. We plan to have one ready within the next couple of months.
2. There is not yet a Sophos version (the anti-virus software supported by Nebula ) released in Nebula that is compatible with Windows 10. The vendor has released a compatible version, but Nebula has a policy of not deploying the latest version to avoid “broken” versions (which have happened often enough in the past to justify this). If a newer Sophos version doesn’t come out by 8/30/2015, we’ll manually override our policy to address this.
3. We have not yet had a chance to evaluate and implement the configuration settings needed to support Windows 10 in a managed environment like ours.
4. We do not yet support basic computer inventory or software distribution to Windows 10. This capability is blocked by a project to update our software delivery and management system. With the Nebula file service design change complete and more engineering resources available in September, we plan to complete this in September.

With respect to #3, we expect that some of these settings will represent major changes to the status quo. For some of these settings, we are still waiting on information from Microsoft while for others, we simply need time to figure out what’s new and plan our desired design. For example, with Windows 10 Microsoft plans to change how updates work. We know this means our existing mechanism that allows customers to defer IE upgrades has reached its end (Microsoft’s stated end of life for IE8-10 on 1/12/2016 is another reason that mechanism has reached end of life) . But Microsoft hasn’t fully shared the details of the update options it imagines for enterprise customers, so we still need time to evaluate what our approach will be.

If you do choose to deploy Windows 10 in Nebula at this time, you should expect that we will implement settings that will affect you later.

Special New Capabilities

Nebula plans to build a new operating system deployment mechanism. We’re hoping to provide an automated upgrade in place experience as part of this new mechanism, which would save you time and money, cut down on our overall costs, and improve our future agility to new operating system releases. We do not have an estimate for when this capability will be ready–it partially depends on the project to update our software deliver and management system, but also will require additional work. We’re hoping to have this ready in the Fall timeframe.

Consequences of a New Windows OS

Nebula has long had a policy of supporting the most recent OS, plus one prior OS, with a grace period for previous OSes, but hasn’t been especially clear which OSes were specifically supported. That’s been addressed in a new document: https://it.uw.edu/wares/nebula/operating-system-and-browser-support/

The short version with respect to Windows 10 is that it’s supported, but with limited capabilities (see above). We’ll continue to consider Windows 7 supported as the prior OS we will continue to support. After we’ve addressed #1-4 noted above, we’ll consider Windows 8.1 to be in a grace status for a year–in other words, we’d like anyone running Windows 8.1 to upgrade to Windows 10. We’re choosing to drop support for Windows 8.1 instead of Windows 7, following Microsoft’s lead in terms of the support it is providing.

The intention here is not to inconvenience anyone, but to encourage everyone to move to a well-supported operating system, so we’ll tweak our plans as needed to follow that intention. So if for some reason, we don’t provide the automated upgrade capability for quite a long time, we’ll extend the grace period for Windows 8.1.

Changing from Nebula2 to UW NetID login 

The Nebula service has set a goal for its UW-IT customers to stop using their Nebula2 user accounts and switch to using their NETID user accounts before April 2015. This is part of a larger initiative consolidating Windows domains, supports the IM Infrastructure Refresh project, and is a blocker for several other Nebula goals such as splitting off a separate Software Distribution Service.

Any customer can make the switch themselves. Hundreds of other Nebula customers have made the switch to only using a NETID user account, and there is no risk to trying the switch because you can revert back to using the Nebula2 user account. There is helpful documentation to assist customers that want to do this self-service at https://it.uw.edu/wares/nebula/contact-us/news/netid-logins/.

Alternatively, Nebula will provide 30 minutes of assistance (at no additional cost beyond the Nebula core fee) to help customers make the switch. We will have dedicated staff available during a specific period for your UW-IT division, but you can also send a request for help at any time to help@uw.edu. If you believe you are no longer using your Nebula2 user account, you can send a request to disable the account, which will help you ensure you don’t have any hidden lingering dependencies on it.

UW file service comparisons 

If you have been wondering what your options are for file sharing now that the H and I drive usage will become billable service, a cost and file comparison list has been compiled and ready for your viewing. Just click this link to view the following chart to compare the capabilities provided by various UW file services.

We have also included information on the differences between the H:drive and the U:drive. More on this is here.

We are approaching the 1^st FY16 monthly billing cycle for Nebula. This is an informational update so you have a chance to update information feeding that billing cycle. We are also providing an update on our plans related to removing Nebula resources that are not claimed (paid for).

What and When:

Earlier today, Nebula processed all the eligibility groups for departments for the first time, re-assigning users based on the membership of your eligibility group.

This was the bulk user “purge” we asked everyone to patiently wait for—thanks for waiting, it saved us a lot of time and kept our costs down. For many reasons, we didn’t actually purge any users—we simply just marked users who no one claimed for their department for later action (more about that below). If you review your users in MyIT, you will see that it reflects your eligibility groups.

Nebula will submit billing charges for July 2015 at the end of the month.

You can review your expected charges for Nebula file services and Nebula desktops via MyIT. What is represented in MyIT is based on 3 things:

1. Which desktops are assigned to your department
2. Which users are in your department’s eligibility group, which by extension determines which Nebula home directories are associated with your department
3. Which shared file service paths or Windows file service paths are assigned to your department

You can expect that what you see in MyIT is what we’ll submit billing charges for.

With respect to our plans for Nebula resources who have no one willing to pay for them, here are our intentions:

• We will remove access to the home directories of users who are no longer in an eligibility group. All Nebula home directories have a snapshot with a 1 year retention beyond deletion, so even if something is undesired now but you later need access, this is a fallback. We plan to delay deletion of undesired home directories for a month to provide a grace period for mistakes.
• We will remove access to shared file service paths which have no department assigned. Prior to doing so, we plan to contact all users who have access to the file service path to let them know of the impending action, so there is an opportunity for a department to step forward and pay to continue. Again, we plan to delay deletion for a month to provide a grace period.

There are other Nebula configuration we will take action on in the future. Future actions we’ll take include removing “unclaimed” user accounts (and by extension access) on the shared file services, removing access to Nebula VPN services, and removing the “Nebula supported” flag which the UW-IT service desk uses in routing requests.

What you need to do:

The mechanisms we’ve created over the last 4 months and may not be as accurate as everyone would like. Since there will be billing charges based on these soon as well as the additional actions I mentioned, it would be best to fix up any inaccuracies now.

If you are a contact for a Nebula department, here are the specific things you should do to review:

• Go to MyIT and review the ‘Users in My Department’ report: https://support.nebula.washington.edu/myIT/myNebulaUsers.aspx. This should only include the users in your eligibility group. If there are missing or additional users, you need to update your eligibility group. NOTE: if you visited MyIT this morning, you are very likely to see a different set of users listed now because we processed the eligibility groups for the first time today. We plan to process eligibility groups once daily, so if you do make changes, you should expect MyIT to reflect those changes the following day.
• Go to MyIT and review the ‘File Services’ report: https://support.nebula.washington.edu/myIT/fileServices.aspx. This should only include those group directories and home directories for your department (i.e. that you will pay for). If there are missing or additional paths, then send a request to help@uw.edu to resolve the file service assignments. If the amount of usage for a given file service path is unexpectedly large, you may want to take action to reduce the use to reduce your cost. If there are home directories you do not want, you can adjust your eligibility group membership. If you do not want to remove a user from your eligibility group, but also don’t want that user to have a Nebula home directory, we have a solution for that, but at this time you’ll need to send a request to help@uw.edu for that solution.

We are aware of a number of eligibility groups which have no members, and have separately already contacted departments where this is the case. You may need to take action if you were contacted about that.

We are aware of several shared file service paths which have no department assigned to them because our initial assignment was requested to be removed. As noted above, we plan to contact the users with access to these locations. You may need to take action if you are contacted about that in the future.

More info:

If you are wondering what a Nebula eligibility group is—see http://www.washington.edu/itconnect/wares/nebula/tools/view-and-manage-nebula-resources/#What.

If you are having problems getting your eligibility group to have the right set of users, we can provide a list of which users were associated with your department prior to today.

That document includes a variety of assistance for departmental contacts who use MyIT to review their Nebula use. We are happy to help you if you need further assistance or explanation—just send us a request at help@uw.edu.