Contact us

Windows Server 2012 ESU Ends October 2026: Are You Ready?

Back To Resources



Load More

FREQUENTLY ASKED QUESTIONS

Commercials
How much does Cloudhouse cost? Down Arrow

Cloudhouse costs are split into two elements – the licensing required to deploy application compatibility packages, and the professional services needed to create the application compatibility packages.

Licensing is offered on a per user basis for desktop applications and a per server basis for server applications. There are discounts available based on volumes.

Professional Services costs are dependent on the nature and complexity of the application. We quote a cost for packaging once we have been able to see the application, or portfolio of applications.

Contact us here with your requirements and we will provide you with a quote.

Packaging and Maintaining Applications
Who is responsible for packaging desktop and server applications? Down Arrow

Cloudhouse provide the Professional Services to package applications.

Requirements for Test and Development Down Arrow

Cloudhouse recommend packaged applications are tested in the standard UAT environments used for natively installed applications, or applications packaged in App-V. The more representative the test environment is of the live environment, the greater the chance of finding any issues prior to go-live.

Updating Applications Down Arrow

Service packs and updates can be applied to the applications in a package using the Editor, refer to Updating, Editing and Maintaining Containers which describes how a new snapshot is created for the update, and how it is then applied to the package.

Operations
Who manages Cloudhouse operationally within an account? Down Arrow

Cloudhouse recommends the same team who manage the operations of native apps.

Automation and Deployment Down Arrow

Applications running in Application Compatibility Packages can be deployed, and managed with same tools, or scripts used to deploy natively installed applications e.g. SCCM, InTune, LAN Desk. Please refer to Supported 3rd Party Products and Versions for details.

Support
How do we know which of our departments/ teams should support the Package? Down Arrow

The Cloudhouse Package does not include OS components, it only contains the packaged application plus Cloudhouse components. Cloudhouse recommend the same team that is responsible for supporting applications packaged with App-V, or delivered as natively installed applications, support Cloudhouse Application Compatibility Containers.

Documentation for Service Desk & Service Management Down Arrow

Full documentation is made available to Cloudhouse partners and customers as required.

Training
Do Cloudhouse provide training? Down Arrow

Cloudhouse offers a full packaging service that can scale to meet any requirement. In the event, however, that a partner wishes to offer application compatibility packaging as part of a wider solution, Cloudhouse will work with that partner. Please contact us here for details.

Agents don’t know your apps are old

Back To Resources



Load More

FREQUENTLY ASKED QUESTIONS

Commercials
How much does Cloudhouse cost? Down Arrow

Cloudhouse costs are split into two elements – the licensing required to deploy application compatibility packages, and the professional services needed to create the application compatibility packages.

Licensing is offered on a per user basis for desktop applications and a per server basis for server applications. There are discounts available based on volumes.

Professional Services costs are dependent on the nature and complexity of the application. We quote a cost for packaging once we have been able to see the application, or portfolio of applications.

Contact us here with your requirements and we will provide you with a quote.

Packaging and Maintaining Applications
Who is responsible for packaging desktop and server applications? Down Arrow

Cloudhouse provide the Professional Services to package applications.

Requirements for Test and Development Down Arrow

Cloudhouse recommend packaged applications are tested in the standard UAT environments used for natively installed applications, or applications packaged in App-V. The more representative the test environment is of the live environment, the greater the chance of finding any issues prior to go-live.

Updating Applications Down Arrow

Service packs and updates can be applied to the applications in a package using the Editor, refer to Updating, Editing and Maintaining Containers which describes how a new snapshot is created for the update, and how it is then applied to the package.

Operations
Who manages Cloudhouse operationally within an account? Down Arrow

Cloudhouse recommends the same team who manage the operations of native apps.

Automation and Deployment Down Arrow

Applications running in Application Compatibility Packages can be deployed, and managed with same tools, or scripts used to deploy natively installed applications e.g. SCCM, InTune, LAN Desk. Please refer to Supported 3rd Party Products and Versions for details.

Support
How do we know which of our departments/ teams should support the Package? Down Arrow

The Cloudhouse Package does not include OS components, it only contains the packaged application plus Cloudhouse components. Cloudhouse recommend the same team that is responsible for supporting applications packaged with App-V, or delivered as natively installed applications, support Cloudhouse Application Compatibility Containers.

Documentation for Service Desk & Service Management Down Arrow

Full documentation is made available to Cloudhouse partners and customers as required.

Training
Do Cloudhouse provide training? Down Arrow

Cloudhouse offers a full packaging service that can scale to meet any requirement. In the event, however, that a partner wishes to offer application compatibility packaging as part of a wider solution, Cloudhouse will work with that partner. Please contact us here for details.

Mastering change in tech environments

Back To Resources

We are now in full swing with our Service Management series and are back for part 3! If you missed parts 1 or 2 you can catch up here. This week’s topic is about managing change within a technology infrastructure and the importance of this within Service Management as a whole. We continue our journey of building solid foundations and ensuring change is not only carried out but that it happens successfully. 

Making change happen

Change is at the heart of progress when it comes to Service Management, however, orchestrating it effectively within complex environments can be a challenge. It’s not just about implementing new systems or updating existing features, it’s about ensuring these changes fit seamlessly into the current estate. This means evaluating the environment, implementing changes, and trialling them – making sure they happen at the right time in the right place and are successful. 

Fulfilling change promises 

Change initiatives often come with grand promises of dramatically improving tech, but that’s not always the case, sometimes they’re just a small adjustment to keep things running smoothly for both the organisation and customers. A crucial step in change management is evaluating the change post-implementation – ensuring all that was promised actually followed through. For instance, if the change was meant to solve an issue or update a particular system, the team should check this actually happened and all the parts are now working as expected. 

Successfully carrying out change is one thing, but it is important to make sure the required change happens to all of the necessary items, not just some of them, and at the right time. By proactively planning and considering the need for change to align with the organisation’s requirements, the team can effectively manage the transition process. With these measures in place, the team can prioritise and stay ahead of the change and ensure that it is carried out in the desired timeframe. As a result, the likelihood of any disruptions or system outages is minimised. 

Navigating successful change initiatives

If you’ve read our previous blogs in this series, you’ll know exactly what Guardian is and how it can help with your Service Management needs. If you haven’t, then check out the last blog post for the low down – Enhancing incident management: How to streamline your efficiency.

Previously, we’ve discussed how Guardian is a great partner to have in the realm of Service Management, but let’s delve into how it can specifically assist you in change management. One of Guardian’s key roles is overseeing changes and monitoring upcoming ones, relieving the Change Management team of this responsibility and allowing them to focus their efforts on enabling change to occur and undertaking their vital oversight function. 

If you wish to discuss this topic further or just come and say hello, we will be at DTX Europe on the 4th and 5th of October – located in booth L30 in the ServiceDesk zone.

Not attending DTX Europe this year? Get in contact today, to discover how Cloudhouse can help you.



Load More

FREQUENTLY ASKED QUESTIONS

Commercials
How much does Cloudhouse cost? Down Arrow

Cloudhouse costs are split into two elements – the licensing required to deploy application compatibility packages, and the professional services needed to create the application compatibility packages.

Licensing is offered on a per user basis for desktop applications and a per server basis for server applications. There are discounts available based on volumes.

Professional Services costs are dependent on the nature and complexity of the application. We quote a cost for packaging once we have been able to see the application, or portfolio of applications.

Contact us here with your requirements and we will provide you with a quote.

Packaging and Maintaining Applications
Who is responsible for packaging desktop and server applications? Down Arrow

Cloudhouse provide the Professional Services to package applications.

Requirements for Test and Development Down Arrow

Cloudhouse recommend packaged applications are tested in the standard UAT environments used for natively installed applications, or applications packaged in App-V. The more representative the test environment is of the live environment, the greater the chance of finding any issues prior to go-live.

Updating Applications Down Arrow

Service packs and updates can be applied to the applications in a package using the Editor, refer to Updating, Editing and Maintaining Containers which describes how a new snapshot is created for the update, and how it is then applied to the package.

Operations
Who manages Cloudhouse operationally within an account? Down Arrow

Cloudhouse recommends the same team who manage the operations of native apps.

Automation and Deployment Down Arrow

Applications running in Application Compatibility Packages can be deployed, and managed with same tools, or scripts used to deploy natively installed applications e.g. SCCM, InTune, LAN Desk. Please refer to Supported 3rd Party Products and Versions for details.

Support
How do we know which of our departments/ teams should support the Package? Down Arrow

The Cloudhouse Package does not include OS components, it only contains the packaged application plus Cloudhouse components. Cloudhouse recommend the same team that is responsible for supporting applications packaged with App-V, or delivered as natively installed applications, support Cloudhouse Application Compatibility Containers.

Documentation for Service Desk & Service Management Down Arrow

Full documentation is made available to Cloudhouse partners and customers as required.

Training
Do Cloudhouse provide training? Down Arrow

Cloudhouse offers a full packaging service that can scale to meet any requirement. In the event, however, that a partner wishes to offer application compatibility packaging as part of a wider solution, Cloudhouse will work with that partner. Please contact us here for details.

Meet Cloudhouse at DTX Europe 2023

Back To Resources

If you’ve been following our Service Management series up to this point, you’ll know that we’re going to be at DTX Europe this year. We wanted to use the series to demonstrate our focus at DTX Europe: Service Management and the surrounding elements that keep it ticking. 

So, it’s time to give you all the details you need to find us at the event. Whether you want to discuss any of the aspects covered in the series further or just want to say hello, we’re a friendly bunch so do make sure you visit us. 

When?

Wednesday, 4 October: 09:30 – 17:30

Thursday, 5 October: 09:30 – 16:30

Where?

Venue: ExCeL London

Zone: ServiceDesk

Stand: L30

Located near: Next to the IT Ops and Service Management Stage

The interesting stuff

Our CTO, Nick, is giving a talk titled ‘The Long Shadow of IT: Orderly society or the Wild West?’ on Thursday afternoon, so make sure you come along and have a listen! All location details for the speech are listed below:

Stage: IT Ops and Service Management

Date: Thursday, October 5th

Time: 12.10pm – 12.35pm

We’ll also be available at our stand all day, for both days, to chat about and demonstrate our trusted product, Guardian. We’re giving full demos so you’ll be able to see the tool in action and get any questions you may have about it answered. 

Guardian is a configuration drift detection and management system that allows businesses to continuously monitor their entire system estate for updates and potential threats. So if this sounds like something you’re interested in or just want to gain a bit more insight about, come and see us at our stand. 

The important stuff

If you haven’t already registered for DTX Europe 2023, here’s the link to do so! We look forward to seeing you!Not attending DTX Europe this year? Get in touch today to discover how Cloudhouse can help you.



Load More

FREQUENTLY ASKED QUESTIONS

Commercials
How much does Cloudhouse cost? Down Arrow

Cloudhouse costs are split into two elements – the licensing required to deploy application compatibility packages, and the professional services needed to create the application compatibility packages.

Licensing is offered on a per user basis for desktop applications and a per server basis for server applications. There are discounts available based on volumes.

Professional Services costs are dependent on the nature and complexity of the application. We quote a cost for packaging once we have been able to see the application, or portfolio of applications.

Contact us here with your requirements and we will provide you with a quote.

Packaging and Maintaining Applications
Who is responsible for packaging desktop and server applications? Down Arrow

Cloudhouse provide the Professional Services to package applications.

Requirements for Test and Development Down Arrow

Cloudhouse recommend packaged applications are tested in the standard UAT environments used for natively installed applications, or applications packaged in App-V. The more representative the test environment is of the live environment, the greater the chance of finding any issues prior to go-live.

Updating Applications Down Arrow

Service packs and updates can be applied to the applications in a package using the Editor, refer to Updating, Editing and Maintaining Containers which describes how a new snapshot is created for the update, and how it is then applied to the package.

Operations
Who manages Cloudhouse operationally within an account? Down Arrow

Cloudhouse recommends the same team who manage the operations of native apps.

Automation and Deployment Down Arrow

Applications running in Application Compatibility Packages can be deployed, and managed with same tools, or scripts used to deploy natively installed applications e.g. SCCM, InTune, LAN Desk. Please refer to Supported 3rd Party Products and Versions for details.

Support
How do we know which of our departments/ teams should support the Package? Down Arrow

The Cloudhouse Package does not include OS components, it only contains the packaged application plus Cloudhouse components. Cloudhouse recommend the same team that is responsible for supporting applications packaged with App-V, or delivered as natively installed applications, support Cloudhouse Application Compatibility Containers.

Documentation for Service Desk & Service Management Down Arrow

Full documentation is made available to Cloudhouse partners and customers as required.

Training
Do Cloudhouse provide training? Down Arrow

Cloudhouse offers a full packaging service that can scale to meet any requirement. In the event, however, that a partner wishes to offer application compatibility packaging as part of a wider solution, Cloudhouse will work with that partner. Please contact us here for details.

Enhancing incident management: How to streamline your efficiency

Back To Resources

Welcome to the second instalment in our newly launched Service Management series! In this blog post, we explore the pivotal role of effective incident management and the importance of data in achieving smooth service delivery. We’re also going to discuss how you can use specific tools to enhance your incident management process and as a result, heighten efficiency. 

Building foundations

In order to build effective incident management systems, you’ll need to start by understanding what it actually means to efficiently resolve incidents. 

At its core, incident management involves the resolution of unforeseen disruptions in service delivery. This could be due to a fault in the system, a change that has gone undetected, a change that didn’t quite go according to plan, human error or many other reasons. A good incident management process has the ability to swiftly navigate and overcome any hiccups, big or small, and restore systems to their normal operations while ensuring minimal impact. 

Effective incident management usually comes down to having the right data, at the right time, for the right job. Having the right tools and the right data at the right time can improve resolution time, improve customer satisfaction and enhance the profile of your Incident handling teams within the organisation.

Guardian – the ultimate tool

Cloudhouse Guardian is a powerful, vendor-agnostic tool that continuously monitors your entire technology estate, providing transparency into the changes occurring in your environment – approved, or not. By providing critical data to understand incidents, Guardian expedites the resolution process, allowing the Incident Management team to quickly address disruption. This not only saves resources and time but also enhances incident detection and management automatically.

With its versatile capabilities that help streamline incident handling, Guardian excels in collecting and processing data, providing valuable insights for swift and accurate resolutions. Integrating this tool with your incident management framework enables organisations to quickly respond to incidents and mitigate potential damage. 

When seamlessly integrating Guardian into your Service Management processes, it silently performs essential work in the background; detecting and notifying the incident team of any issues. This ensures swift action and efficient resolution. To learn more about Guardian’s role in service management, check out the previous episode in this series – Navigating the world of Service Management.

All about the data 

In today’s fast-paced environment, the ability to handle unexpected disruptions quickly and effectively is crucial. Guardian enriches your existing Incident Management framework by providing transparency into the environment. However, Guardian doesn’t just speed up the process, it also produces valuable data for your Service Management teams to utilise in the future. Analysing the data helps to determine likely causes and patterns in disruption that can then be addressed proactively to minimise disruption or eliminate them altogether. 

So, to reiterate the point made at the beginning of this blog, effective Incident Management is all about having the right data, at the right time, for the right job. 

If you wish to discuss this topic further or just come and say hello, we will be at DTX Europe on the 4th and 5th of October – located in booth L30 in the ServiceDesk zone.

Not attending DTX Europe this year? Get in contact today, to discover how Cloudhouse can help you.



Load More

FREQUENTLY ASKED QUESTIONS

Commercials
How much does Cloudhouse cost? Down Arrow

Cloudhouse costs are split into two elements – the licensing required to deploy application compatibility packages, and the professional services needed to create the application compatibility packages.

Licensing is offered on a per user basis for desktop applications and a per server basis for server applications. There are discounts available based on volumes.

Professional Services costs are dependent on the nature and complexity of the application. We quote a cost for packaging once we have been able to see the application, or portfolio of applications.

Contact us here with your requirements and we will provide you with a quote.

Packaging and Maintaining Applications
Who is responsible for packaging desktop and server applications? Down Arrow

Cloudhouse provide the Professional Services to package applications.

Requirements for Test and Development Down Arrow

Cloudhouse recommend packaged applications are tested in the standard UAT environments used for natively installed applications, or applications packaged in App-V. The more representative the test environment is of the live environment, the greater the chance of finding any issues prior to go-live.

Updating Applications Down Arrow

Service packs and updates can be applied to the applications in a package using the Editor, refer to Updating, Editing and Maintaining Containers which describes how a new snapshot is created for the update, and how it is then applied to the package.

Operations
Who manages Cloudhouse operationally within an account? Down Arrow

Cloudhouse recommends the same team who manage the operations of native apps.

Automation and Deployment Down Arrow

Applications running in Application Compatibility Packages can be deployed, and managed with same tools, or scripts used to deploy natively installed applications e.g. SCCM, InTune, LAN Desk. Please refer to Supported 3rd Party Products and Versions for details.

Support
How do we know which of our departments/ teams should support the Package? Down Arrow

The Cloudhouse Package does not include OS components, it only contains the packaged application plus Cloudhouse components. Cloudhouse recommend the same team that is responsible for supporting applications packaged with App-V, or delivered as natively installed applications, support Cloudhouse Application Compatibility Containers.

Documentation for Service Desk & Service Management Down Arrow

Full documentation is made available to Cloudhouse partners and customers as required.

Training
Do Cloudhouse provide training? Down Arrow

Cloudhouse offers a full packaging service that can scale to meet any requirement. In the event, however, that a partner wishes to offer application compatibility packaging as part of a wider solution, Cloudhouse will work with that partner. Please contact us here for details.

Navigating the world of Service Management

Back To Resources

As we gear up for DTX Europe on the 4-5th October 2023, we’re excited to be starting a new series dedicated to everything Service Management. The aim of this series is to understand the importance of Service Management while exploring how to implement it seamlessly into service delivery. 

To kick off, let’s start by unravelling the foundations of Service Management, its role in delivering great customer experiences and some of the challenges. 

What is Service Management and why is it important?

The role of ‘Service Management’ is to provide services to IT that enable the smooth delivery of services to end users or consumers of them. Service Management teams tend to follow ITIL-based frameworks and processes. This enables them to deliver services in a standard way and benefit from industry best practices. 

You will likely know them as the Service Desk, Change Management, Configuration Management and Service Delivery teams, each with their own core responsibilities but together ensuring that IT delivers and runs services to a standard set of practices with the minimum of disruption to the rest of the organisation.

Service Management detection and challenges 

So what does service management actually entail? There are several practices and they vary from organisation to organisation but essentially you will have a group handling Incidents (interruptions to services that are unplanned or unexpected by the consumer of that service), Problems (looking at systemic issues within the IT Infrastructure and services), Change Management/Enablement (ensuring that change within the infrastructure and applications is undertaken in a coordinated fashion and with as little disruption to consumers as possible) and Configuration Management (Configuration Managers are responsible for ensuring that the IT estate is understood, provide a point of reference and documented, usually but not necessarily in a CMDB supporting the other teams in their goals).

For instance, at Cloudhouse, if an issue affects more than 50 people and persists for a long time, it is known as a ‘major incident.’ This term emphasises the urgency and scale of the issue; demanding immediate attention. When an issue persists and is not easily resolved, Service Management professionals begin a ‘problem investigation.’ This phase requires an examination of the technical infrastructure. The objective is to uncover the probable causes behind the issue or a series of related issues. 

Service Management teams work to determine where the issue started, what caused it, and how it has developed (if at all). The first step they need to take is to look over the last 24 hours; combing through recent changes and activity to pinpoint what might have triggered an error in the system. It could be due to a software update, a security breach or a software bug.

After sifting through the possibilities and once the Service Management teams have identified the cause, they then look into fixing it. Once they have identified a fix, they engage the Change Management/Enablement teams to identify the best time for implementation, while understanding the urgency, risk and approach for minimising impact to those unaffected. Additionally, the teams will ensure that the plans are in place to ensure the problem is not only resolved but also prevented from recurring.

The scenario above is of course a vastly simplified scenario and situations and conditions vary from organisation to organisation so your mileage may differ. However, as a high-level illustration, this is the general approach.

Simplifying Service Management

How can we help you enhance and enrich your Service Management processes? Cloudhouse Guardian is a configuration drift detection and management system that allows businesses to continuously monitor their entire system estate for updates and potential threats. As well as many other benefits, it allows your Service Management teams to have visibility over their systems and reduces the time taken to identify changes that have occurred within your estate. Ultimately cutting down the time to get an issue resolved and a customer back up and running. 

If you wish to discuss this topic further or just come and say hello, we will be at DTX Europe on the 4th and 5th of October – located in booth L30 in the ServiceDesk zone.

Not attending DTX Europe this year? Get in contact today, to discover how Cloudhouse can help you.



Load More

FREQUENTLY ASKED QUESTIONS

Commercials
How much does Cloudhouse cost? Down Arrow

Cloudhouse costs are split into two elements – the licensing required to deploy application compatibility packages, and the professional services needed to create the application compatibility packages.

Licensing is offered on a per user basis for desktop applications and a per server basis for server applications. There are discounts available based on volumes.

Professional Services costs are dependent on the nature and complexity of the application. We quote a cost for packaging once we have been able to see the application, or portfolio of applications.

Contact us here with your requirements and we will provide you with a quote.

Packaging and Maintaining Applications
Who is responsible for packaging desktop and server applications? Down Arrow

Cloudhouse provide the Professional Services to package applications.

Requirements for Test and Development Down Arrow

Cloudhouse recommend packaged applications are tested in the standard UAT environments used for natively installed applications, or applications packaged in App-V. The more representative the test environment is of the live environment, the greater the chance of finding any issues prior to go-live.

Updating Applications Down Arrow

Service packs and updates can be applied to the applications in a package using the Editor, refer to Updating, Editing and Maintaining Containers which describes how a new snapshot is created for the update, and how it is then applied to the package.

Operations
Who manages Cloudhouse operationally within an account? Down Arrow

Cloudhouse recommends the same team who manage the operations of native apps.

Automation and Deployment Down Arrow

Applications running in Application Compatibility Packages can be deployed, and managed with same tools, or scripts used to deploy natively installed applications e.g. SCCM, InTune, LAN Desk. Please refer to Supported 3rd Party Products and Versions for details.

Support
How do we know which of our departments/ teams should support the Package? Down Arrow

The Cloudhouse Package does not include OS components, it only contains the packaged application plus Cloudhouse components. Cloudhouse recommend the same team that is responsible for supporting applications packaged with App-V, or delivered as natively installed applications, support Cloudhouse Application Compatibility Containers.

Documentation for Service Desk & Service Management Down Arrow

Full documentation is made available to Cloudhouse partners and customers as required.

Training
Do Cloudhouse provide training? Down Arrow

Cloudhouse offers a full packaging service that can scale to meet any requirement. In the event, however, that a partner wishes to offer application compatibility packaging as part of a wider solution, Cloudhouse will work with that partner. Please contact us here for details.

Humanising IT: The importance of openness and collaboration

Back To Resources

As technology develops and AI begins to reshape our environment, it can sometimes be easy to overlook the human aspect of IT. Human-centric technology focuses on prioritising user experiences and needs when designing and implementing IT solutions. By placing users at the forefront of these developments, organisations can create transformative systems that not only meet user expectations but also drive successful IT rollouts.

Gartner reported that a staggering 75% of all IT projects in the US are deemed unsuccessful by those who initiated them. This serves as compelling evidence of the need for effective change management and addressing scepticism within teams when it comes to implementing technology changes. By exploring human-centric technology and promoting openness and collaboration, successful IT initiatives can be achieved. 

Understanding human-centric technology

Focusing on the human-centric side of technology allows organisations to shift their perspective from purely functional to prioritising the needs and experiences of actual people. As previously mentioned, a human-centric approach focuses on the desires and pain points of the users, creating accessibility and simplicity that best suits them in order to get the greatest outcome. By using this approach, technology can become more than just a tool, it can transform and enhance the usability experience.

In the realm of IT initiatives, being open and collaborative is extremely important. Embracing these principles can bring technology projects to life, making them dynamic and transformative. Involving stakeholders from different departments and levels in the decision-making process allows for a diverse range of perspectives and expertise. This collaborative approach improves decision quality and ensures that solutions align with the organisation’s unique needs and challenges. By fostering an open environment, innovative solutions can be brought to life and transform an organisation’s IT estate for the better. 

A business’s technology is not just built for the IT team, so it is important to consider an open and collaborative approach. Gaining insight into other teams’ needs can be hugely beneficial as it enhances satisfaction in multiple teams, resulting in a positive perspective of IT initiatives and therefore reducing any friction when it comes to adopting new systems. 

Overcoming resistance to change

Implementing IT changes and upgrades can be met with resistance, especially from individuals who don’t see the need for new IT rollouts. Understanding the reasons for this scepticism is crucial for addressing concerns during implementation. One common reason for resistance is fear of the unknown – people who are uncertain about how the changes will affect their daily routines and job roles are likely to resist. The complexity of new technologies can also create apprehension, as individuals may worry about their ability to adapt. 

To address concerns during IT implementation, proactive strategies can help. As previously stated, involving employees and stakeholders in decision-making fosters ownership and empowers them to contribute their insights, making them more open to the idea of change. Offering training and support resources equips individuals with the skills and knowledge to embrace new technologies confidently and effectively.

Creating a culture that embraces change and views IT initiatives as growth opportunities is essential. By fostering an environment that values collaboration, feedback, and experimentation, organisations can pave the way to a future where IT changes are a motivation for growth and advancement, rather than sources of resistance.

At Cloudhouse, we are experts in IT implementation and specialise in providing technology solutions that prioritise human-centric experiences. Our products, Alchemy and Guardian, help businesses enhance their user experience and remodel their technology landscape. Contact us today to explore how we can elevate your IT initiatives.



Load More

FREQUENTLY ASKED QUESTIONS

Commercials
How much does Cloudhouse cost? Down Arrow

Cloudhouse costs are split into two elements – the licensing required to deploy application compatibility packages, and the professional services needed to create the application compatibility packages.

Licensing is offered on a per user basis for desktop applications and a per server basis for server applications. There are discounts available based on volumes.

Professional Services costs are dependent on the nature and complexity of the application. We quote a cost for packaging once we have been able to see the application, or portfolio of applications.

Contact us here with your requirements and we will provide you with a quote.

Packaging and Maintaining Applications
Who is responsible for packaging desktop and server applications? Down Arrow

Cloudhouse provide the Professional Services to package applications.

Requirements for Test and Development Down Arrow

Cloudhouse recommend packaged applications are tested in the standard UAT environments used for natively installed applications, or applications packaged in App-V. The more representative the test environment is of the live environment, the greater the chance of finding any issues prior to go-live.

Updating Applications Down Arrow

Service packs and updates can be applied to the applications in a package using the Editor, refer to Updating, Editing and Maintaining Containers which describes how a new snapshot is created for the update, and how it is then applied to the package.

Operations
Who manages Cloudhouse operationally within an account? Down Arrow

Cloudhouse recommends the same team who manage the operations of native apps.

Automation and Deployment Down Arrow

Applications running in Application Compatibility Packages can be deployed, and managed with same tools, or scripts used to deploy natively installed applications e.g. SCCM, InTune, LAN Desk. Please refer to Supported 3rd Party Products and Versions for details.

Support
How do we know which of our departments/ teams should support the Package? Down Arrow

The Cloudhouse Package does not include OS components, it only contains the packaged application plus Cloudhouse components. Cloudhouse recommend the same team that is responsible for supporting applications packaged with App-V, or delivered as natively installed applications, support Cloudhouse Application Compatibility Containers.

Documentation for Service Desk & Service Management Down Arrow

Full documentation is made available to Cloudhouse partners and customers as required.

Training
Do Cloudhouse provide training? Down Arrow

Cloudhouse offers a full packaging service that can scale to meet any requirement. In the event, however, that a partner wishes to offer application compatibility packaging as part of a wider solution, Cloudhouse will work with that partner. Please contact us here for details.

Exploring the fallibility & trustworthiness of AI: Can we really rely on Artificial Intelligence?

Back To Resources

Understanding the hype & reality of AI

Artificial Intelligence (AI) has undoubtedly become one of the most significant technological advancements to date. Its potential to revolutionise industries, automate processes, and enhance decision-making has sparked excitement and curiosity among professionals, as well as the general public. However, amidst the hype surrounding AI, it is essential to consider its limitations and challenges to understand whether we can genuinely rely on this transformative technology.

In the last year, AI has made substantial progress in various fields, such as healthcare, finance and customer service. The algorithms that power AI allow the technology to learn from data input and as a result make decisions automatically. These capabilities have made AI hugely popular among many industries and organisations seeking to optimise their day-to-day operations. 

However, there are some negatives to AI which will be discussed in this blog – but do they outweigh the good? This leads us to the important question of “Is AI fallible or trustworthy?”

AIs limitations & challenges

While AI has shown remarkable capabilities, it is important to acknowledge its limitations. A significant issue is that AI lacks human-like decision-making functions, causing a difference in its decision-making process compared to humans. This difference can lead to inconsistencies between AI-generated results and human expectations, potentially resulting in unwanted outcomes. It is also important to note that while AI appears to act on its own, data scientists are still extremely important as they are required to input the information the technology runs on.

Relying solely on AI can be risky, especially when building an entire business around it. Businesses need to develop strategies for managing AI failures and ensuring that human oversight is always available when needed – helping to avoid any detrimental damage or delay to business operations if there is an outage on their chosen AI system. 

A final point to consider when using AI is that it will always be outdated. As human knowledge is gained faster than it can be transferred into the databases, it is impossible to update it at the same speed – the latest version of ChatGPT is currently running on data from September 2021. While this is not detrimental to its functionality it is important to be wary of this. 

Robust testing, reliable results & vulnerability

To ensure the trustworthiness of AI-generated results, it is essential to conduct thorough testing and validation procedures. Circling back to data scientists and their role in developing AI; they are in charge of creating the criteria for what constitutes “good” and “bad” data when it comes to AI models. There is only so much input humans can have so it is important that users of the technology ensure the accuracy of their questions, making it easier for AI to reach a reliable answer. 

The integration of AI in DevOps and DevSecOps teams also requires careful planning and consideration. It is essential for developers to identify potential vulnerabilities and address security concerns – as advanced as AI systems may seem, they are not immune to cyber threats and breaches can potentially lead to an alteration in the decision-making processes. 

The balance between embracing AI & ensuring accountability 

While AI continues to offer great potential, it is vital to find a balance between embracing its benefits and ensuring accountability for its fallibility. The idea of AI completely taking over human jobs may be exaggerated, as it is more likely to complement human abilities rather than replace them.

AI’s real value lies in its ability to handle mundane tasks and mirror human decision-making. By understanding the limitations and challenges of AI, organisations can make informed decisions about its implementation and leverage its potential while mitigating risks. However, it can be tricky to know exactly what to do to avoid such risks by using a generalised AI system. It is advised that businesses that are using AI use a specialised approach to automation in order to keep their technology secure. 

Cloudhouse has been successfully offering a solution that does exactly that for years – Guardian is a configuration drift detection and management system that allows businesses to continuously monitor all of the systems within their estate for updates, compliance changes and potential threats. Giving businesses the visibility of their systems and allowing them to manage progress and change while improving their security level. AI requires careful management, human oversight, and robust testing to ensure its reliability and trustworthiness. As AI continues to evolve, our understanding of its capabilities and limitations will play a crucial role in maximising its benefits while minimising potential drawbacks.

To discover how Cloudhouse can help you, get in contact today. 

 



Load More

FREQUENTLY ASKED QUESTIONS

Commercials
How much does Cloudhouse cost? Down Arrow

Cloudhouse costs are split into two elements – the licensing required to deploy application compatibility packages, and the professional services needed to create the application compatibility packages.

Licensing is offered on a per user basis for desktop applications and a per server basis for server applications. There are discounts available based on volumes.

Professional Services costs are dependent on the nature and complexity of the application. We quote a cost for packaging once we have been able to see the application, or portfolio of applications.

Contact us here with your requirements and we will provide you with a quote.

Packaging and Maintaining Applications
Who is responsible for packaging desktop and server applications? Down Arrow

Cloudhouse provide the Professional Services to package applications.

Requirements for Test and Development Down Arrow

Cloudhouse recommend packaged applications are tested in the standard UAT environments used for natively installed applications, or applications packaged in App-V. The more representative the test environment is of the live environment, the greater the chance of finding any issues prior to go-live.

Updating Applications Down Arrow

Service packs and updates can be applied to the applications in a package using the Editor, refer to Updating, Editing and Maintaining Containers which describes how a new snapshot is created for the update, and how it is then applied to the package.

Operations
Who manages Cloudhouse operationally within an account? Down Arrow

Cloudhouse recommends the same team who manage the operations of native apps.

Automation and Deployment Down Arrow

Applications running in Application Compatibility Packages can be deployed, and managed with same tools, or scripts used to deploy natively installed applications e.g. SCCM, InTune, LAN Desk. Please refer to Supported 3rd Party Products and Versions for details.

Support
How do we know which of our departments/ teams should support the Package? Down Arrow

The Cloudhouse Package does not include OS components, it only contains the packaged application plus Cloudhouse components. Cloudhouse recommend the same team that is responsible for supporting applications packaged with App-V, or delivered as natively installed applications, support Cloudhouse Application Compatibility Containers.

Documentation for Service Desk & Service Management Down Arrow

Full documentation is made available to Cloudhouse partners and customers as required.

Training
Do Cloudhouse provide training? Down Arrow

Cloudhouse offers a full packaging service that can scale to meet any requirement. In the event, however, that a partner wishes to offer application compatibility packaging as part of a wider solution, Cloudhouse will work with that partner. Please contact us here for details.

So many stakeholders... providers, consumers, interested parties... oh my!

Back To Resources

In May, we introduced the topic of how to be successful with Configuration Management Databases (CMDB) this is the 2nd in our blog series on the topic and in this post, we’ll be going over how to onboard and manage stakeholders into Configuration Management.

As a Configuration Manager, one of the expectations many have for your role and the processes and tools you support is that they will be a magic bullet and solve the world’s problems. Of course, we all know this is an unreasonable expectation! Configuration Management is a supporting set of processes and tools which enrich everything they interact with. Because of the disconnect in expectation vs reality, it is important that those that own Configuration Management processes and tools are clear about the role they play.

Onboarding new groups, teams or tools into the Configuration Management ecosystem can be fraught with challenges. The largest obstacle to overcome is usually ensuring that people understand that Configuration Management owns very little data, whether that is published into the CMDB or consumed by the consumers of the CMDB. Data is owned, and always owned, by those that publish it – if there are issues or errors in data then the owner must be accountable for resolving the errors.

The needs of Configuration Management are varied and onboarding new groups who have sources of data you need is critical as the goal is to enrich and provide the highest quality data to the consumers. BUT you must ensure you are not onboarding providers of data for the mere sake of doing so, you have to have a consumer for any data you onboard, otherwise, things will get messy fast! it is easier to add data than take extraneous data out of your Configuration Management tools.

Based on this, it is important to ensure your Configuration Management Policy contains clear criteria for data onboarding – When do you research new data sources? How will you assess potential data sources? You must also ensure the data you onboard is ‘worthy’ of inclusion in your Configuration Management data published for consumers. Is it reliable? Is it appropriate? Is it of sufficient quality? All these questions need to have guidelines for assessment to provide the quality data your consumers expect and deserve.

Onboarding consumers of Configuration Management is more difficult than providers of data because you need to understand their needs to a detailed level. If you don’t take the time to do that your CMDB and other tools will become cluttered with data your consumers don’t need. It is critical that when you onboard new consumers, you have a structured methodical approach where you build close relationships, and understand the processes they expect your data to support and the touchpoints between you, your data and their needs. Ideally, as a result of onboarding a consumer, you should be able to build a map between each attribute of data and the consuming endpoint. Yes, you will most likely have multiple consumers for a given attribute. This is a GOOD thing! The more shared data in your ecosystem, the more supportive of the business needs your Configuration Management becomes and thus is seen to be delivering core business value.

So to summarise: onboard data from providers only when you have a use case to fulfil for that data; understand the consumer needs, what the data means to them and the work they are trying to achieve with the data you are providing; keep a map of consumers vs the data you hold; and keep in touch with both providers and consumers to ensure value delivery for your organisation.

 

Next time we’ll discuss approaches for managing your CMDB and Configuration Management practices ‘in-life’ so you continue to deliver value and also ensure Configuration Management remains relevant within your organisation.

 

Stephen Earl, Product Manager

 



Load More

FREQUENTLY ASKED QUESTIONS

Commercials
How much does Cloudhouse cost? Down Arrow

Cloudhouse costs are split into two elements – the licensing required to deploy application compatibility packages, and the professional services needed to create the application compatibility packages.

Licensing is offered on a per user basis for desktop applications and a per server basis for server applications. There are discounts available based on volumes.

Professional Services costs are dependent on the nature and complexity of the application. We quote a cost for packaging once we have been able to see the application, or portfolio of applications.

Contact us here with your requirements and we will provide you with a quote.

Packaging and Maintaining Applications
Who is responsible for packaging desktop and server applications? Down Arrow

Cloudhouse provide the Professional Services to package applications.

Requirements for Test and Development Down Arrow

Cloudhouse recommend packaged applications are tested in the standard UAT environments used for natively installed applications, or applications packaged in App-V. The more representative the test environment is of the live environment, the greater the chance of finding any issues prior to go-live.

Updating Applications Down Arrow

Service packs and updates can be applied to the applications in a package using the Editor, refer to Updating, Editing and Maintaining Containers which describes how a new snapshot is created for the update, and how it is then applied to the package.

Operations
Who manages Cloudhouse operationally within an account? Down Arrow

Cloudhouse recommends the same team who manage the operations of native apps.

Automation and Deployment Down Arrow

Applications running in Application Compatibility Packages can be deployed, and managed with same tools, or scripts used to deploy natively installed applications e.g. SCCM, InTune, LAN Desk. Please refer to Supported 3rd Party Products and Versions for details.

Support
How do we know which of our departments/ teams should support the Package? Down Arrow

The Cloudhouse Package does not include OS components, it only contains the packaged application plus Cloudhouse components. Cloudhouse recommend the same team that is responsible for supporting applications packaged with App-V, or delivered as natively installed applications, support Cloudhouse Application Compatibility Containers.

Documentation for Service Desk & Service Management Down Arrow

Full documentation is made available to Cloudhouse partners and customers as required.

Training
Do Cloudhouse provide training? Down Arrow

Cloudhouse offers a full packaging service that can scale to meet any requirement. In the event, however, that a partner wishes to offer application compatibility packaging as part of a wider solution, Cloudhouse will work with that partner. Please contact us here for details.

Why are CMDB’s so hard? Some thoughts to set you up for success:

Back To Resources

Let’s take this back a step and just remind ourselves of what a Configuration Management Database (CMDB) is supposed to be. The CMDB was born in the days of ITIL v2 when Configuration Management was introduced as a formal process within the framework.

The goal of a CMDB is to provide a repository that can be deemed authoritative for all the things an organisation cares about, there are philosophical debates and discussions about what a ‘thing’ is but they are separate from what a CMDB is intended to accomplish. Normally a ‘thing’ would be a server, a piece of network equipment, Desktop PC or Laptop and even things like HVAC systems and in some cases, we’ve seen Laundry equipment and lightbulbs be stored there.

Whatever a customer wants to track, apply Change Management processes to or deems important enough to reference on an ongoing basis likely belongs in a CMDB. 

Once defined the next step is to work out what information you actually want to hold about those things, the attributes of interest. Many CMDB tools will come with a prebuilt data model for this but that doesn’t mean you have to follow that data model in your situation. The normal guidance would be to adhere to the provided model and deviate only where you need to and I would go along with that approach. In fact, in previous lives, I’ve had many conversations with organisations around how to fit esoteric devices into the packaged data models and 99% of the time we’ve found a home with appropriate attributes provided out of the box, so don’t overthink how unique your requirements are as it might be they likely aren’t.

Only store what you need to meet the needs of your consumers, what do I mean by consumers? Well, think about how the data in your CMDB is going to be used within the business, what reports, processes or activities will make use of your CMDB data? These are what you are building the CMDB for, do NOT fall into the trap of ‘dumping everything into the CMDB’ and then ‘working out what you’ll use it for later’. All that happens is your data will build up, become stale and be deemed useless and die on the vine. Your CMDB WILL fail, and by fail I mean it will not be used for the purposes it was created, data will not be maintained, you will not find owners for the data held in it and thus it will be seen as a problem rather than a solution to business challenges.

Do not over promise. Building a CMDB is a significant undertaking and requires effort, quite a lot of effort to be fair, this effort is from all areas of the business not just IT or the Configuration Management team. Consumers have input, Configuration Managers are the control point, data providers also contribute significantly to the implementation. Everyone has their role to play and this alone makes the implementation of CMDB ‘hard.’

Critical to the success of building and maintaining your CMDB is a Configuration Management Policy. One of the key elements here is defining what ‘things’ are interesting enough to be stored in the CMDB, with this in place everyone has a common understanding of ‘if’ something should be in the CMDB and then expectations are managed and set appropriately. Of course, this is not a one-time definition and depending on your situation you will want to review the criteria of ‘interesting’ as and when you deem fit. Critically, do not leave this on the shelf, keep it alive, keep it refreshed and keep it relevant.

The key to CMDB success is truly being transparent, communicative and sharing the vision of what Configuration Management means to your organisation, the contribution it will make and the value it will bring. Never lose sight of the value!

This is the first in a set of blog posts we’ll be making on the topic of CMDB. In our next thrilling instalment, (I know you are all on the edge of your seats!) we’ll talk about managing the stakeholders, strategies for on boarding and also how do you look after, feed and water the beast you are creating and keep it happy so it can continue to provide the value your organisation is investing in.

That’s it for now!

Stephen Earl, Product Manager



Load More

FREQUENTLY ASKED QUESTIONS

Commercials
How much does Cloudhouse cost? Down Arrow

Cloudhouse costs are split into two elements – the licensing required to deploy application compatibility packages, and the professional services needed to create the application compatibility packages.

Licensing is offered on a per user basis for desktop applications and a per server basis for server applications. There are discounts available based on volumes.

Professional Services costs are dependent on the nature and complexity of the application. We quote a cost for packaging once we have been able to see the application, or portfolio of applications.

Contact us here with your requirements and we will provide you with a quote.

Packaging and Maintaining Applications
Who is responsible for packaging desktop and server applications? Down Arrow

Cloudhouse provide the Professional Services to package applications.

Requirements for Test and Development Down Arrow

Cloudhouse recommend packaged applications are tested in the standard UAT environments used for natively installed applications, or applications packaged in App-V. The more representative the test environment is of the live environment, the greater the chance of finding any issues prior to go-live.

Updating Applications Down Arrow

Service packs and updates can be applied to the applications in a package using the Editor, refer to Updating, Editing and Maintaining Containers which describes how a new snapshot is created for the update, and how it is then applied to the package.

Operations
Who manages Cloudhouse operationally within an account? Down Arrow

Cloudhouse recommends the same team who manage the operations of native apps.

Automation and Deployment Down Arrow

Applications running in Application Compatibility Packages can be deployed, and managed with same tools, or scripts used to deploy natively installed applications e.g. SCCM, InTune, LAN Desk. Please refer to Supported 3rd Party Products and Versions for details.

Support
How do we know which of our departments/ teams should support the Package? Down Arrow

The Cloudhouse Package does not include OS components, it only contains the packaged application plus Cloudhouse components. Cloudhouse recommend the same team that is responsible for supporting applications packaged with App-V, or delivered as natively installed applications, support Cloudhouse Application Compatibility Containers.

Documentation for Service Desk & Service Management Down Arrow

Full documentation is made available to Cloudhouse partners and customers as required.

Training
Do Cloudhouse provide training? Down Arrow

Cloudhouse offers a full packaging service that can scale to meet any requirement. In the event, however, that a partner wishes to offer application compatibility packaging as part of a wider solution, Cloudhouse will work with that partner. Please contact us here for details.