On May 30 and July 2, Juriba's CTO, Barry Angell, presented a session entitled 'How to get your executive management fired up about Evergreen IT after your Windows 10 migration' at the Ivanti Windows 10 Summit. The conference was hosted entirely online and it is still available to watch on-demand.

A few weeks ago, I participated in two interesting sessions at the Microsoft Ignite Tour: one about Microsoft Autopilot, which we have extensively covered in the past, and one about Desktop Analytics, which is the forthcoming upgrade to Microsoft's Windows Analytics telemetry tool. With the release due shortly, we thought we would share some information on this significant update.

Last month, we partnered with Flexera to present the webinar entitled "Time is up for Windows 7: How to position your organization for Windows 10 and beyond" hosted by myself and Adam Jeffries, Senior Solution Engineer at Flexera.

We all know that hindsight is always 20/20. There is probably nothing more frustrating than realizing that you just made a huge mistake, and then looking back and realizing that you should have known that that was a bad idea. But sometimes, we also receive really bad advice that overrides our gut feeling or better judgement.

Whatever caused the misstep, we all learn from mistakes — but it's always easier to learn through someone else's mistakes. So, we compiled below the worst pieces of advice we have ever heard on the topic of managing an effective IT Transformation. This way, if you hear one of these common myths, you'll know to be wary of it and consider it twice.

Last week, I had the pleasure of hosting a webinar with our partner Flexera entitled "Time is up for Windows 7: How to position your organization for Windows 10 and beyond". If you missed it or you had to drop out during it, don't worry — you can access the on-demand version below.

Over the past few years, we have seen our fair share of failed and dangerously inefficient enterprise attempts to keep Windows 10 and Office 365 Servicing up-to-date. Often, the organization took longer than anticipated to run through the first initial migration, skipped an update to come up for air, just to drown under the workload of the feature update roll out, for which it had vastly underestimated the risk and work effort. Ever worse, these updates are often managed manually, with antiquated and inadequate project management practices!

If you recently tried to find anything on Microsoft Office — for example on the enterprise section of Office.com — you might have noticed that there isn't much mention of Microsoft's on-premise productivity application suite anymore.

The vast majority of Microsoft's marketing communication and sales conversation is about Office 365! This is not an oversight or a temporary marketing campaign — but rather a strategic push to move enterprise customers away from the perpetually licensed Office fat client and onto the subscription-based, always up-to-date Office 365. Moreover, now that Office 2019 is about to be released, many enterprises are asking themselves: "Should we consider Office 2019, or is it not the right time to switch to Office 365 ProPlus?"

Rolling out Office 365 can be very exciting considering the value it will add to your organization in terms of unified communication, collaboration, and business processes! But it can be equally terrifying if you think about all the dependencies of users, mailboxes, delegates, mail archives, public folders, groups, instant messaging, ... the list goes on and on.

After the initial migration is completed, Microsoft will release two larger Office client feature updates and monthly security updates to increase productivity for your end users and tighten security. However, just like Windows as a Service, these larger feature updates will need to be rolled out effectively as they can also be considered a mini-migration.

Last week, we spoke about how to negotiate a successful Windows 10 or Office 365 migration deal with a service integrator. But what happens once the contracts are signed? Should you sit back and let them take the reigns completely or is there something you can do to ensure the success of this project?

Some enterprises assume that because they just hired an expert organization to take this project off their hands, they can simply drop the ball and let the integrator pick it up and run with it. But while your outsourcer brings a tremendous value to the table, it is completely unrealistic to expect that they will do the best job possible without associated input from your side.

On January 14th, 2020, the extended support for Windows 7 ends, which means that enterprises have about 26 months to fully roll out Windows 10. Similarly, Microsoft expects that at least two-thirds of its Office business customers will move to Office 365 by fiscal year 2019. Since a migration project of that size will take, on average, more than 124 man weeks to complete, it is about high time to get serious about upgrading!

According to our own research, only 44% of organizations are set on managing this IT Transformation internally; 28% are about to issue a Request-for-Proposal, 14% have not decided yet, and 14% have already engaged with a service integrator to outsource this massive project.

It's October — and that means budget rounds for many organizations! Years ago, this was a rather straightforward exercise; you knew how much money you needed to keep the lights on, and then decide which projects you were planning in the coming year. For example, if you wanted to upgrade to the new Windows OS, you would calculate your program length, divide the cost by the number of years and create an investment case.

But times have changed and Evergreen IT requires not only a different approach to calculating your budget but also advanced buy-in from your executives. We have talked about both in the past. Like it or not, Evergreen IT requires a funding plan, and without one, the chances of repeating the mistakes of the past are high. Today, we want to take a closer look at how to create a waterproof business case for your Evergreen IT management to ensure it gets approved.

Most of our customers are currently in the process of deciding 1) which Windows 10 Upgrade Management strategy to pursue (6,  12, 18 or 24 months), and whatever they are choosing, 2) how to achieve the velocity they need to get everything ready and tested to roll everything out in the defined period.

To manage your Windows 10 upgrades efficiently and with maximum velocity, there are a lot of upfront activities that have to be done first, e.g., getting a new build image ready, testing your hardware, planning your deployment rings, and more.

To the surprise of many, Microsoft announced on September 6th, 2019, that it will retire its Windows Analytics services in favor of Desktop Analytics. While the reality of Desktop Analytics (DA) replacing Windows Analytics was expected at some point, the timing is surprising as Desktop Analytics is still in Public Preview and the deadline is in just 4.5 months.

To get customers ready, Microsoft is encouraging everyone to start evaluating Desktop Analytics now because new customers will no longer have access to Windows Analytics Upgrade Readiness and Device Health once DA becomes generally available. Customers using “Update Compliance” in their Azure portal already can continue to do so — even after January 2020.

Last week, we took a closer look at how the Agile Software Development methodology and its concepts could be used to manage your IT estate the Evergreen IT way. Recently, we have been getting some questions about Agile in general and how to use Dashworks in that context. Since Juriba's IT Transformation and Evergreen IT Management platform is specifically designed to find the optimal path of maximum velocity to accelerate deployment in enterprise IT environments, Agile is a natural fit.

To walk through the process using an example, let's say we are migrating to the latest version of Windows 10. Since we are already late in the game, this migration has to serve as a preparation for future upgrade cycles as well and needs to be managed as tightly as possible to make repeatable and industrialized.

Traditionally, enterprises tackled large IT transformation projects such as OS migrations, infrastructure upgrades, or email migrations, one at a time in what is commonly termed a "big bang" approach.

These projects would often take between 12-36 months and were repeated every five to six years — or only when absolutely necessary. After years of Business As Usual (BAU) running, project sponsors would quickly add other items to the scope, resulting in project delivery that almost always went over budget, past the due date and cost a fortune.

LONDON, 3 July 2019 -- Juriba has announced that its flagship software Dashworks has been accepted into the G-Cloud 11 framework, part of the UK Government’s digital marketplace.

It's been a long time coming, but it is finally here — our brand-new Windows-as-a-Service Management Project Plan Template! And I am thrilled to finally share with you some details on it.

This brand-new project plan template is the sequel to our extremely successful Windows 10 Enterprise Migration Project Plan that was originally published in September of 2015. While the previous project plan focused on the initial migration to Microsoft's new operating system, this new project plan enables technology executives, IT pros, and BAU managers to plan and execute their ongoing Windows-as-a-Service update management in the most effective way possible.

LONDON, 2 July 2018 -- Juriba has announced that its flagship software Dashworks has been accepted into the G-Cloud 10 framework, part of the UK Government’s digital marketplace.

If you look at how IT traditionally spent its investment dollars, there would be a distinct requirement for a positive return on investment by the end of the first three years. Many were long-term IT investments that would determine how you would operate in the next ten to twelve years, and resulted in the definition of many established IT management practices.

But those ancient IT processes and policies used to manage legacy apps are inadequate to handle modern technology updates. Today, most enterprises are much more agile, having moved applications into the cloud, or utilizing the power of Software-as-a-Service. However, most are still maintaining a layer of dinosaur legacy applications and other mission-critical on-premise software in massive data centers. Since most IT organizations are unable or unwilling to change how they manage IT, they still use IT processes and policies that date back more than twenty years!

The quality of customer service has a massive impact on how consumers interact with the service provider — whether that provider is an internal department, an outsource partner, or a company providing goods and services externally. Studies have shown that one out of two customers will stop doing business with a company because of a poor service experience.

That is why most consumers, 71% in fact, prefer firms that give them the ability to solve most service issues on their own. While this might not surprise you, it might shock you to know that an astonishing 38% of consumers would rather clean a toilet than speak to a customer service representative!

In the last few years, enterprise IT departments have faced a unique set of challenges: On the one hand, they have morphed from a supporting entity to a business enabler, and are maintaining increasingly complex IT landscapes whilst battling significantly larger cyber security threats than ever before. On the other hand, they have to manage more change with fewer resources and stagnant or minimally-increasing budgets.

A few weeks ago, we spoke about the Digital Workplace and how it came a long way from being an abstract concept that a lot of companies saw value in, but did not have the technology to support their needs properly, to becoming a reality for a lot of enterprises as they embraced server-hosted virtual desktops.

As organizations are now embarking on their Windows 10 migrations, as well as considering Evergreen IT as a long-term IT goal in order to become more agile, scalable and flexible, Virtual Desktop Infrastructure is experiencing a technology-induced revival. It's been a much slower adoption than many analysts expected, but more companies are now virtualizing desktops than ever before!

Gartner expected the hosted virtual desktop market to grow to 76 million users by the end of this year. And it seems the growth is not slowing down anytime soon. Most analysts forecast anywhere from 8.9% CAGR (IDC for the entire VCC market) up to 27% (depending on the analysts' definition of VDI) during the period 2016-2020. 

As more and more enterprises are starting to embrace Virtual Desktop Infrastructure to save costs, tighten security and improve manageability and compliance as well as give their employees more device flexibility and accessibility options, many fail to consider the generational change in the workforce that is happening right now. 

Microsoft has been buzzing this week with announcements around the future of its Windows 10 Servicing model — so much that one announcement almost fell through the cracks: the public preview release of the software giant's cloud-connected service Desktop Analytics.

Originally announced with much fanfare in September 2018, Desktop Analytics was described as a cloud service that integrates with System Center Configuration Manager and is aimed to make application compatibility assessment before a Windows 10 or Office 365 upgrade/migration easier. In addition, the free tool was supposed to provide migration suggestions, help create optimized pilot groups for testing, and allow IT managers to create quick inventories of in-house Windows apps to make compatibility checks simpler. Or, in Microsoft's words, it would "take the guess work out of testing and focus your attention on key blockers."

Traditionally, User Acceptance Testing (UAT) is performed at the end of a long software development cycle by the intended audience under real-world conditions. By then, engineering has performed a battery of technical tests to ensure the software works as expected. However, in some cases, engineering's understanding of the business requirements and user needs versus what the user was actually looking for are two very different things. This is where UAT usually comes in.

Today, we are wrapping up our 3-part blog post series about Evergreen IT by taking a closer look at software catalogs.

(If you have missed the previous blog posts you can find them here: Software Asset Lifecycle Management - Dream or Reality as well as How Important Is Application Normalization For Your Next Windows 10 Migration And Evergreen IT?)

As your organization evolves, and demand for business flexibility increases, the proliferation of applications each end user works with tends to grow in volume as well. Consequently, your IT department works to cope with an increasingly complicated application environment, and you begin to dream of initiating a Software Asset Lifecycle Management project that will bring order to the chaos. 

What’s the name of that application Employee A is running on her desktop? Is it the same as the similar title running on another computer by Employee B in a nearby department? You cannot get an accurate idea of how much software you have deployed if you don’t know the names and locations of each installed application.

If software is not named consistently, you might see one copy that includes the name of the vendor and another that has a truncated or abbreviated version of the same name, or a different vendor entirely (think Macromedia and Adobe - both now Adobe Systems). It might seem like you have five applications when actually you only have five names for the same thing.

A stressed out, harried IT department is a sign that your organization has bitten off more than it can chew. There’s no need to have circumstances lead to the point where your IT professionals are pulling out their hair in frustration and growing ragged from lack of sleep because of the burden that comes from launching one big bang project after the other.

Instead, gradual, incremental changes to your mission-critical software assets will be much more effective and will help your organization stay on track. Many larger organizations have recognized this not only as a possible way to gain a long-term competitive advantage but also a way to significantly cut cost and resources. 

In this 3-part series, we are exploring vital stepping stones that pave the way to achieving this. Last week, we talked about software asset lifecycle management, and today we will look into application normalization. In a few days, we will take a closer look at software cataloging. With that in mind, you may be wondering how important application normalization is to your Windows 10 and Evergreen IT projects.

Today, enterprises need to be able to adapt faster to changing environments to fend off competitive pressure; they need to be able to grow faster or scale back when needed — all while reducing costs and increasing the value of the services offered.

There is not a week that goes by where I don't have at least one conversation about Evergreen IT or managing IT change as "Business as Usual" with prospects, customers or partners. 

The demand for managing information technology assets on a continual basis reflects a natural consequence of software developments (e.g., cloud computing, software-as-a-service) as well as changing business demands. Think about your Apple or Android phone constantly updating applications in the background, or Windows 10 and its regular patches.

But back in the corporate world, the requirement for control of the environment is a significant hurdle to adopting the most adaptive change methodologies. Imagine if an untested change brought down your main trading application! The challenge is how to take a better approach but retain control. Ideally, Evergreen IT results in increased efficiencies, more agility and better scalability across the entire enterprise. For example, IT transformations could be managed in an agile fashion (business as usual), rather than in one-off big bang migration projects. 

 With the Windows 2003 Server end of life time bomb now passed on July 14^th 2015, we thought we would take the time to document our advice for Server 2003 migration project planning activities based on our own server migration experience. Download our Server 2003 Project Plan for free.

At Juriba, we believe all our customers deserve access to valuable and free education on our products.

2018 was the busiest year for our development team here at Juriba so we thought it might be useful to put out a summary of the major changes. As customer requests for functionality grow so does the product, hence the increasing need to provide more updates, more frequently, and the release of two major new versions of Dashworks (5.2 and 5.3).

With Windows 7 approaching end of support in January 2020, most enterprises are accelerating plans to migrate to Windows 10 in 2018 to take advantage of the new or improved cyber-security capabilities, and avoid an expensive custom support agreement  with Microsoft. However, at this time, fewer organizations than expected have taken the plunge because they dread the Windows-as-a-Service servicing model that requires continuous upgrades and a more agile, Evergreen IT management approach.

Ahead of the game is Pillsbury Winthrop Shaw Pittman LLP, an international law firm recognized by the Financial Times as one of the Most Innovative Law Firms three years running. Today, I want to share a little sneak peek at our latest customer case study and tell you the story of how Dashworks transformed this dreaded Windows 10 migration experience into an IT Transformation initiative that the 700+ lawyers and their staff could not only get behind, but actively participate in!

Rolling out Office 365 can be very exciting considering the value it will add to your organization in terms of unified communication, collaboration, and business processes! But it can be equally terrifying if you think about all the dependencies of users, mailboxes, delegates, mail archives, public folders, groups, instant messaging, ... the list goes on and on.

After the initial migration is completed, Microsoft will release two larger Office client feature updates and monthly security updates to increase productivity for your end users and tighten security. However, just like Windows as a Service, these larger feature updates will need to be rolled out effectively as they can also be considered a mini-migration.

At Juriba, we believe all our customers deserve access to valuable and free education on our products.

LONDON, 3 July 2019 -- Juriba has announced that its flagship software Dashworks has been accepted into the G-Cloud 11 framework, part of the UK Government’s digital marketplace.

The Juriba team

Juriba was formed in 2008 by a team of industry veterans who have spent their lives managing, operating and migrating enterprise desktops and infrastructure.

It's hard to believe, but on October 15, 2018 Juriba turned 10 so we thought we'd write about our journey! It all started in 2008 from Julia Bell's (our Chief Operating Officer) house and 7 million assets migrated later, Juriba has achieved 10 years in business. We thought it would be nice to celebrate with all our readers by listing our key milestones in this blog post.