‎Jul 15 2024

10:33 AM

As a business owner or team leader, you may find yourself in a situation where you need to add other team members to a calendar appointment that has already been booked by a customer. This can be a bit tricky, but don’t worry – I’m here to help! In this blog post, we’ll go over the steps you can take to add other team members to a calendar appointment that shows up on your calendar.

Step 1: Check Your Calendar Settings

Before we dive into the steps for adding team members to a calendar appointment, it’s important to check your calendar settings to ensure that your team members are visible on your calendar. To do this, go to your calendar settings and make sure that “Show Team Members” is turned on. This will allow you to see your team members on your calendar and add them to appointments as needed.

Step 2: Open the Appointment

To begin, open the appointment on your calendar that was booked by the customer. You should see all of the details of the appointment, including the date, time, and any other relevant information.

Step 3: Click on “Add Guest”

Next, click on the “Add Guest” button on the right-hand side of the appointment window. This will open a new window where you can search for your team members.

Step 4: Search for Your Team Members

In the “Add Guest” window, type in the name of the team member you want to add to the appointment. You can also filter by role or department to find the right person more quickly. Once you’ve found the team member you want to add, click on their name to select them.

Step 5: Add the Team Member to the Appointment

After selecting the team member you want to add, they will be automatically added to the appointment on your calendar. You can repeat these steps for each team member you want to add to the appointment.

Step 6: Save the Changes

Finally, once you’ve added all of the team members you want to include in the appointment, be sure to save the changes. This will ensure that all team members are visible on your calendar and that everyone is aware of the appointment details.

Tips and Tricks

Here are a few tips and tricks to keep in mind when adding team members to a calendar appointment:

* Make sure to check your calendar settings before you begin to ensure that your team members are visible on your calendar.

* Use the “Add Guest” button to quickly search for and add team members to the appointment.

* Be sure to save the changes after adding all team members to ensure that everyone is aware of the appointment details.

* Consider using a shared calendar to keep track of all appointments and events for your team. This can help ensure that everyone is on the same page and that no one double-books an appointment.

Conclusion

Adding team members to a calendar appointment can be a bit tricky, but with these simple steps, you should be able to do it with ease. By following these steps and using a few tips and tricks, you’ll be able to ensure that all of your team members are aware of the appointment details and can plan accordingly. Happy scheduling!

VMware NSX: The Future of Security Infrastructure

In today’s digital age, security is a top priority for organizations of all sizes and industries. With the increasing threat of cyber attacks and data breaches, it’s more important than ever to have a robust security infrastructure in place to protect sensitive information and systems. One solution that is gaining popularity is VMware NSX, a network virtualization platform that makes security intrinsic to the infrastructure.

Traditional security approaches rely on separate security devices and appliances that are often scattered throughout the network, making it difficult to maintain consistent policy enforcement across all components of an application. This can lead to vulnerabilities and gaps in security coverage, leaving organizations open to attacks. VMware NSX changes this by integrating security into the infrastructure itself, providing consistent, automatic enforcement of security policies for every component of an application, regardless of workload type or underlying physical hardware.

With VMware NSX, organizations can implement a number of advanced security features, such as micro-segmentation, that were previously only available on high-end security appliances. Micro-segmentation allows organizations to break up their network into smaller, isolated segments, each with its own set of security policies. This helps to limit the spread of attacks and prevent unauthorized access to sensitive data. Additionally, VMware NSX provides advanced threat protection features, such as intrusion detection and prevention, that can detect and block sophisticated threats before they reach the network.

One of the key benefits of VMware NSX is its ability to provide consistent security enforcement across all components of an application, regardless of workload type or underlying physical hardware. This means that organizations can apply the same security policies to all applications and workloads, without having to worry about compatibility issues or manually configuring security settings for each individual component. This approach not only simplifies security management but also helps to ensure that all components of an application are equally secure, reducing the risk of vulnerabilities and attacks.

Another advantage of VMware NSX is its ability to integrate with other security tools and systems, such as identity and access management (IAM) solutions, to provide a comprehensive security framework. For example, organizations can use IAM solutions to manage user identities and access rights across the network, while VMware NSX provides advanced threat protection and intrusion detection features to detect and block unauthorized access attempts. This integrated approach to security helps to ensure that all components of an organization’s infrastructure are secure and protected against threats.

In addition to its advanced security features, VMware NSX also offers a number of other benefits for organizations, such as improved network agility and scalability. With VMware NSX, organizations can quickly deploy new applications and workloads, without having to worry about manual configuration or compatibility issues. This helps to speed up the deployment process and improve overall network agility. Additionally, VMware NSX provides a scalable architecture that can grow with the needs of the organization, making it an ideal solution for businesses of all sizes.

In conclusion, VMware NSX is a game-changing technology that is revolutionizing the way we think about security infrastructure. By integrating security into the network itself, VMware NSX provides consistent, automatic enforcement of security policies for every component of an application, regardless of workload type or underlying physical hardware. This approach not only simplifies security management but also helps to ensure that all components of an organization’s infrastructure are secure and protected against threats. With its advanced threat protection features, ability to integrate with other security tools and systems, and improved network agility and scalability, VMware NSX is the future of security infrastructure.

The Future of High-Performance Computing: Intel’s Nehalem Processors and the Power of Turbo Mode

In a recent announcement, BBC News revealed that Intel is set to revolutionize the world of high-performance computing with its new range of Nehalem processors. This latest lineup of chips promises to deliver unparalleled power and efficiency, setting the standard for the next decade. Among the key features of these processors is a groundbreaking technology called Turbo Mode, which enables the chip to adapt to changing workloads and optimize performance. But what exactly is Turbo Mode, and how will it impact the future of computing?

The Turbo Button: A Game-Changer for PC Performance

In recent years, consumers have grown accustomed to the idea of a “turbo button” on their smartphones and other devices. With a single tap, these devices can suddenly unleash a burst of speed and power, delivering lightning-fast performance when needed most. However, until now, this technology has been largely absent from the world of high-performance computing.

Enter Intel’s Nehalem processors, which introduce the concept of Turbo Mode to the PC market. This innovative feature allows the processor to automatically adjust its power consumption and performance based on the workload at hand. When a task requires more processing power, Nehalem’s Turbo Mode kicks in, dynamically increasing the chip’s clock speed and power draw to deliver the necessary performance boost.

Turbo Mode: The Key to Balancing Performance and Efficiency

The beauty of Turbo Mode lies in its ability to balance high performance and energy efficiency. Traditionally, these two goals have been seen as mutually exclusive, with users forced to choose between a powerful system that guzzles energy or an efficient one that sacrifices performance. However, with Nehalem’s Turbo Mode, Intel has found a way to deliver both in one package.

According to Intel, the new range of processors can achieve up to 50% better performance than previous generations while consuming less power. This is achieved through a combination of hardware and software optimizations, including improved cache management, enhanced branch prediction, and intelligent power management.

The Future of Computing: Nehalem and Beyond

With the introduction of Turbo Mode in its Nehalem processors, Intel has set the stage for a new era of high-performance computing. This technology has the potential to revolutionize the way we use our devices, enabling faster, more efficient, and more powerful systems that can adapt to our changing needs.

As we look towards the future, it’s clear that Nehalem is just the beginning. With this latest lineup of processors, Intel has demonstrated its commitment to innovation and pushing the boundaries of what’s possible. As the technology continues to evolve, we can expect to see even more advanced features and capabilities emerge, further blurring the lines between performance and efficiency.

In conclusion, Intel’s Nehalem processors represent a major milestone in the history of high-performance computing. With their groundbreaking Turbo Mode technology, these chips have the potential to transform the way we use our devices, delivering unparalleled power and efficiency in a single package. As we look towards the future, it’s clear that Intel is leading the charge towards a brighter, more powerful tomorrow.

The German Railway (DB) has faced a challenging time during the recent European Football Championship (EM), with many trains running late, overcrowded platforms, and even a train accident causing delays. According to DB’s own admission, the railway network was overwhelmed and struggled to cope with the increased demand during the tournament.

The situation was so dire that some teams, such as the Dutch team, were unable to arrive on time for their scheduled press conferences. In one instance, a train was delayed by 134 minutes due to a wild animal accident, highlighting the unpredictable nature of the railway system. Other issues included overcrowded platforms and traffic violations for football enthusiasts, as reported by the British Guardian and the New York Times.

In response to these challenges, DB has acknowledged that it must accept criticism and take action to improve its services. The company’s external survey (Opinary GmbH) has shown that the railway network is overwhelmed and in need of modernization. According to Berthold Huber, a member of the DB’s management board, the sanitation of the railway network is unavoidable and overdue.

The DB has also released a written statement detailing its efforts during the EM period. The company notes that it transported 12 million passengers during the tournament, with 410 trains in operation daily. Additionally, 14 special trains were run each day, providing an additional 10,000 seats. S-Bahns, regional trains, and buses were also well-utilized, with over 750,000 passengers using the S-Bahn in Berlin alone.

Despite these efforts, the DB has faced several challenges during the tournament. The most significant issue was the high volume of passengers, which overwhelmed the railway network and caused delays. Additionally, some trains were diverted due to flooding, and others were delayed due to a train accident.

To address these challenges, the DB has begun a comprehensive modernization program for its most heavily used corridors. The first phase of this program involves the complete closure of the Frankfurt am Main – Mannheim line for five months, during which time the line will be fully sanitized and modernized. According to Huber, this line is the “heart of the German rail network,” and the modernization will provide up to eight years of “baufrei” (construction-free) time on the line.

The DB has also acknowledged that the ongoing conflict in Ukraine has led to increased costs for the procurement of materials, which has impacted the budget for the modernization program. However, the company remains confident that the additional 30 billion euros provided by the federal government will be sufficient to complete the modernization efforts by 2030.

In conclusion, the DB has faced significant challenges during the recent EM period, including overcrowding, delays, and even a train accident. However, the company is taking steps to address these issues, including a comprehensive modernization program for its most heavily used corridors. Despite the increased costs due to the conflict in Ukraine, the DB remains confident that it can complete the modernization efforts by 2030.

VMware vSphere 4.1: The End of an Era for Guest OS Patching?

In a recent guest post on GestaltIT, Dwayne Lessner, the brains behind IT Blood Pressure, posed an intriguing question: Is My Favourite VSphere Tool Going Away? The answer, it turns out, is yes and no. According to the VMware vSphere 4.1 release notes, the latest version of vCenter Update Manager (VUM) will be the last to allow patching of Windows and Linux guests. This has sparked some debate about the wisdom of this decision, with Dwayne Lessner arguing that it is a bad thing, while I take a different view.

First, let me say that I have never understood why VMware saw it as their job to patch the operating systems running on their guests. In my experience, the vast majority of vSphere administrators use native patching solutions like Windows Server Update Services (WSUS) to keep their guest OSes up to date, rather than relying on VUM. So, while I can understand why some might be upset by this change, I don’t think it will have a significant impact on most vSphere environments.

That being said, there may be some use cases where VUM was the only practical solution for patching guests. For example, in environments where WSUS is not feasible due to network or security constraints, VUM provided a convenient way to keep guests up to date without having to manually apply updates. However, I would argue that these use cases are relatively rare, and that the loss of this feature can only be a good thing.

One of the main benefits of separating patching responsibilities between native solutions like WSUS and VUM is that it allows for greater flexibility and control over the patching process. By using native patching solutions, administrators can more easily manage updates across their environment, without having to rely on a single tool like VUM. Additionally, native patching solutions are often better suited to handle complex update scenarios, such as applying updates to multiple guests at once or rolling back updates that have caused issues.

Furthermore, while I can understand why some might be attached to the idea of using VUM for guest OS patching, I believe that losing this feature can only be a good thing. By focusing on its core strengths – such as patching VMware products and providing centralized management for vSphere environments – VUM can become a more streamlined and effective tool.

In fact, I would argue that the end of guest OS patching in VUM is an opportunity for VMware to explore new features and capabilities that can provide even greater value to its customers. For example, the company could extend VUM’s functionality to include patching for VMware Workstation, Fusion, and Player installations – a feature that would be incredibly useful for many vSphere administrators.

In conclusion, while the end of guest OS patching in VUM may come as a disappointment to some, I believe that it is a positive development for the tool and the industry as a whole. By separating patching responsibilities between native solutions and centralized management tools like VUM, administrators can enjoy greater flexibility and control over their patching processes, leading to more efficient and effective update management. So while we may mourn the loss of this feature, I believe that the future of vSphere patching is bright indeed.

As a seasoned IT professional, I have always been skeptical about the need for vCenter Update Manager (VUM) to patch Windows and Linux guests. In his recent guest post on GestaltIT, Dwayne Lessner, who runs IT Blood Pressure, argues that the upcoming version 4.1 of vSphere will be the last to include this feature, and that it is a bad thing. However, I disagree with this assessment and believe that the removal of guest OS patching from VUM can only be a good thing.

Firstly, I have never understood why VMware saw it as their job to patch the operating systems that the guests are running. It is much more appropriate for “native” patching solutions such as Windows Server Update Services (WSUS) to handle patching of the guests, rather than relying on VUM to do so. WSUS provides a more comprehensive and efficient way of patching the guests, and it also allows IT teams to maintain control over the patching process.

Furthermore, I have yet to see any practical use case for guest OS patching in VUM. In my experience, most organizations prefer to use native patching solutions for their guests, rather than relying on VUM to do so. The only exception might be in cases where the organization does not have a well-defined patch management process, but even then, I would argue that it is better to use a native patching solution rather than relying on VUM.

Moreover, removing guest OS patching from VUM can only be a good thing. It will allow VMware to focus on its core strengths, such as virtualization and cloud computing, rather than trying to be an all-in-one solution for patch management. By leaving patching of the guests to native solutions, IT teams can have more control over the patching process and ensure that their environments are properly maintained.

I do agree with Dwayne that vCenter Update Manager is a valuable tool for patching VMware products, and I would love to see it extended to cover patching of VMware Workstation, Fusion, and Player installations in the enterprise. However, I strongly believe that removing guest OS patching from VUM is a positive move that will benefit IT teams and organizations as a whole.

In conclusion, while Dwayne Lessner may see the removal of guest OS patching from vCenter Update Manager as a bad thing, I firmly believe that it is a positive development that will allow VMware to focus on its core strengths, and provide IT teams with more control over their patching process. Native patching solutions such as WSUS are much better suited for patching the guests, and removing this feature from VUM can only be a good thing.

July 15, 2024

Qubiskicks Error Code 1904: Troubleshooting and Solutions

Are you experiencing Qubiskicks Error Code 1904 on your Windows computer? This error can be frustrating, but there are several troubleshooting steps you can take to resolve the issue. In this article, we will explore the possible causes of Qubiskicks Error Code 1904 and provide step-by-step solutions to fix it.

Causes of Qubiskicks Error Code 1904

————————————

Qubiskicks Error Code 1904 is typically caused by damaged or missing components. This error can occur due to various reasons such as:

* Corrupted system files

* Incorrectly installed software

* Malware infections

* Outdated Windows version

* Insufficient system resources

Solutions to Fix Qubiskicks Error Code 1904

——————————————

To fix Qubiskicks Error Code 1904, follow these steps:

### Step 1: Restart your computer

The first step is to restart your computer. This simple step can often resolve the issue by refreshing your system and clearing any temporary files that may be causing the error.

### Step 2: Run the Qubiskicks Install Diagnostic Tool

The Qubiskicks Install Diagnostic Tool can help identify and fix issues with the installation of Qubiskicks. To run this tool, follow these steps:

* Open the Start menu and search for “Qubiskicks”

* Click on “Qubiskicks Install Diagnostic Tool”

* Follow the on-screen instructions to run the diagnostic test

### Step 3: Enable the built-in Administrator account

If the error persists after running the diagnostic tool, you may need to enable the built-in Administrator account. To do this, follow these steps:

* Open the Start menu and search for “Command Prompt”

* Right-click on “Command Prompt” and select “Run as administrator”

* Type the following command and press Enter:

“`

net user administrator *

“`

This will enable the built-in Administrator account.

### Step 4: Reinstall Qubiskicks

After enabling the built-in Administrator account, reinstall Qubiskicks to ensure that all components are properly installed. To do this, follow these steps:

* Open the Start menu and search for “Qubiskicks”

* Click on “Uninstall Qubiskicks”

* Follow the on-screen instructions to complete the uninstallation process

* Once the uninstallation is complete, download and install Qubiskicks again from the official website

### Step 5: Disable the built-in Administrator account

After reinstalling Qubiskicks, disable the built-in Administrator account to prevent any conflicts with the newly installed software. To do this, follow these steps:

* Open the Start menu and search for “Command Prompt”

* Right-click on “Command Prompt” and select “Run as administrator”

* Type the following command and press Enter:

“`

net user administrator -delete

“`

This will delete the built-in Administrator account.

Conclusion

———-

Qubiskicks Error Code 1904 can be a frustrating issue, but it can be resolved by following these troubleshooting steps. By restarting your computer, running the Qubiskicks Install Diagnostic Tool, enabling and disabling the built-in Administrator account, and reinstalling Qubiskicks, you can fix this error and continue using your Windows computer without any issues.

As we continue to push the boundaries of virtualization and embrace new technologies, one of the key challenges we face is reducing migration times during live updates. In an earlier blog post, we delved into the internals of vMotion and how it works under the hood. Today, we’ll explore some options for lowering migration times even further.

By default, vMotion works beautifully on high-bandwidth networks, but as we move towards faster and more reliable networking technologies, there is always room for improvement. In this blog post, we’ll discuss several ways to tune vMotion for lower migration times, so you can enjoy seamless live updates without any performance hits.

Option 1: Enable NIOVC-Express

One of the most significant bottlenecks during vMotion is the overhead of the virtual machine (VM) memory copy process. To address this, VMware introduced Non-Intrusive Online Virtual Machine Cloning (NIOVC-Express), which significantly reduces the memory copy overhead by using a different clone technique.

To enable NIOVC-Express, follow these steps:

1. Open the vSphere Client and navigate to the ESXi host or cluster you want to configure.

2. Click on “Edit” and select “Advanced Settings.”

3. Scroll down to the “Performance” section and click on “Configure.”

4. Enable the “NIOVC-Express” option.

Once enabled, NIOVC-Express will use a different clone technique that reduces the memory copy overhead, resulting in faster vMotion times. However, keep in mind that NIOVC-Express is only available on VMware vSphere 6.5 and later versions.

Option 2: Use Multi-Threaded vMotion

Another option to lower migration times is by using multi-threaded vMotion. This feature allows the vMotion process to run in parallel, leveraging multiple CPU cores to reduce the migration time.

To enable multi-threaded vMotion, follow these steps:

1. Open the vSphere Client and navigate to the ESXi host or cluster you want to configure.

2. Click on “Edit” and select “Advanced Settings.”

3. Scroll down to the “Performance” section and click on “Configure.”

4. Enable the “Multi-Threaded vMotion” option.

By enabling multi-threaded vMotion, you can take advantage of multi-core CPUs and reduce migration times significantly. However, keep in mind that this feature is only available on VMware vSphere 6.7 and later versions.

Option 3: Optimize Network Settings

Network settings play a crucial role in determining vMotion performance. To optimize network settings for lower migration times, follow these steps:

1. Open the vSphere Client and navigate to the ESXi host or cluster you want to configure.

2. Click on “Edit” and select “Networking.”

3. Select the network you want to optimize and click on “Edit.”

4. Adjust the network settings, such as MTU size, packet burst size, and RSS (Receive Side Scaling) parameters, to optimize vMotion performance.

By optimizing network settings, you can reduce the overhead of the network during vMotion and improve migration times. Keep in mind that the optimal network settings will vary depending on your specific environment and network hardware.

Option 4: Use vSphere Replication

vSphere Replication is another option to lower migration times by replicating VMs across different sites or hosts. By replicating VMs, you can reduce the amount of data that needs to be transferred during vMotion, resulting in faster migration times.

To enable vSphere Replication, follow these steps:

1. Open the vSphere Client and navigate to the ESXi host or cluster you want to configure.

2. Click on “Edit” and select “Storage.”

3. Select the datastore where your VMs are stored and click on “Edit.”

4. Enable the “vSphere Replication” option and select the replication partner.

Once enabled, vSphere Replication will create a replica of your VMs on the replication partner host, reducing the amount of data that needs to be transferred during vMotion. This feature is particularly useful for disaster recovery and business continuity scenarios.

Conclusion

In this blog post, we explored several options for tuning vMotion for lower migration times. By enabling NIOVC-Express, using multi-threaded vMotion, optimizing network settings, and leveraging vSphere Replication, you can reduce the time it takes to migrate VMs during live updates.

Remember that the optimal configuration will vary depending on your specific environment and requirements. Therefore, we recommend testing different configurations in your development environment before deploying them in production.

As always, we encourage you to share your feedback and experiences with vMotion tuning in the comments section below. Happy tuning!

The Evolution of Windows: A Story of Good and Bad

Windows, the operating system that powers millions of computers around the world, has had its fair share of ups and downs over the years. From the early days of Windows 3.11 to the latest release of Windows 7, Microsoft’s flagship product has undergone significant changes and improvements. However, with each new version, there seems to be a pattern of good and bad reviews from users and critics alike.

Let’s take a look at the history of the Windows consumer line and how it has been perceived by the public.

Windows 95 – The Spawn of the Devil?

Released in 1995, Windows 95 was a big change from its predecessor, Windows 3.11. With its new interface and features like the Start menu and Taskbar, it was met with mixed reviews. Some people loved the new look and feel, while others hated it, calling it the “spawn of the devil.” BAD

Windows 98 – A Well-Received Improvement

Next up was Windows 98, which offered improvements to the design and interface. While not revolutionary, it was well received by users and critics alike. GOOD

Windows Me – A Bit of a Battering

Windows ME (Millennium Edition) came next, and it received a bit of a battering from the public. It was criticized for its instability and compatibility issues with older software. BAD

Windows XP – Still Going Strong

Then along came Windows XP, which is still going strong nearly 8 years later. With its sleek interface and improved security features, XP was a hit with users and critics alike. GOOD

Vista – A Platform for Criticism

Next up was Windows Vista, which received a lot of criticism for its perceived lack of improvements over XP, as well as its high system requirements. Google currently returns over 1 million results if you search for “Vista sucks.” BAD

Windows 7 – A Return to Good Graces?

Finally, we have Windows 7, which has generally received good feedback from users and critics alike. With its improved performance, security features, and the same look and feel as Vista, it seems that Microsoft may have finally gotten it right. GOOD

Windows 8 – A New Chapter?

And now, we have Windows 8 already in development. While it’s still early days, only time will tell if this new version of Windows will continue the good trend or fall victim to the same criticisms as its predecessors.

The Pattern of Good and Bad

As we can see from the history of the Windows consumer line, there seems to be a pattern of good and bad reviews. Each new version has its own set of strengths and weaknesses, but overall, Microsoft has made significant improvements over the years. However, it’s clear that the public’s perception of each new version is heavily influenced by the media and general public opinion.

The Future of Windows

Only time will tell what the future holds for Windows. Will Microsoft continue to improve and innovate, or will they fall victim to the same criticisms as previous versions? One thing is certain – the evolution of Windows will continue to be a story of good and bad, but we can only hope that the good will outweigh the bad in the years to come.

Innovative System zur Trinkwasseraufbereitung für Raumanzüge

Eine Forschergruppe der Cornell University hat ein innovatives System entwickelt, das Urin in Trinkwasser umwandeln kann, um langzeitauswärtige Astronauten zu hydratisieren. Das System könnte dazu beitragen, Hygieneprobleme und Wassermangel during spacewalks zu lösen.

Die Forscher haben ein tragbares Filtersystem entwickelt, das Urin in Trinkwasser umwandelt, indem es eine Kombination aus Vorwärts- und Umkehrosmose verwendet. Das System ist schnell und effizient und kann 500 ml Urin in lediglich fünf Minuten in trinkbares Wasser umwandeln.

Das System besteht aus einem Auffangbecher, der die Genitalien umschließt, und einem Filtersystem, das die Flüssigkeit absaugt und reinigt. Ein Feuchtigkeitssensor erkennt, sobald Urin ausgeschieden wird, und schaltet automatisch die Vakuumpumpe ein, die die Flüssigkeit absäuft.

Die Forscher haben verschiedene Methoden untersucht, um den Urin in Trinkwasser umzuwandeln, darunter eine Umkehrosmose, eine Filterung durch Bakterien, die Nutzung von Elektrolyse sowie die Verwendung von Weltraumstrahlung. Sie entschieden sich schließlich für eine Kombination aus Vorwärts- und Umkehrosmose, die eine hohe Reinheit des Wassers bei einem geringen Energieaufwand bietet.

Das entwickelte System ist noch nicht weltraumtauglich und muss unter anderem noch unter Schwerelosigkeit getestet werden, um dort die Funktion zu garantieren. however, the system has the potential to revolutionize the way astronauts stay hydrated during long-duration space missions.

Die Wissenschaftler der Cornell University haben sich durch die Lektüre von Frank Herbert’s “Dune”-Roman inspirieren lassen, der beschreibt, wie ein “Stillsuit” ständig Schweiß und Urin sammelt und in Trinkwasser umwandelt. Die Forscher hoffen, dass ihr System ein ähnliches Hygieneproblem lösen kann.

Das entwickelte System könnte auch bei langzeitauswärtigen Missionen auf der Erde eingesetzt werden, wo die Wasserressourcen begrenzt sind. Es ist ein weiterer Schritt in Richtung einer zukünftigen wasserstoffbasierten Wirtschaft.

In summary, the Cornell University researchers have developed an innovative system for purifying urine to provide drinking water for astronauts during long-duration space missions. The system has the potential to revolutionize the way astronauts stay hydrated and could also be used on Earth for long-term missions in areas with limited water resources.