Use integrated identity information to create and manage identities and control access to enterprise resources. We provide identity and access management, single sign-on (SSO), access governance, and more.

Detect and respond to all potential threats quickly and decisively. By monitoring user activities, security events, and critical systems, we provide actionable security intelligence to reduce the risk of data breach.

A new SPIN on server workloads

My colleague Ken Baker has written a great piece in this month’s Novell Connection magazine, discussing some of the new features of the upcoming releases of PlateSpin Migrate, PlateSpin Protect, and PlateSpin Forge.

I’ll give you a hint, it’s something a lot of you have been waiting for, and it shows how much we still love Novell and our loyal operating platform user base…

Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment. It just worked for at least one person, and perhaps it will be useful for you too. Be sure to test in a non-production environment.

Leave a Comment

A colleague of mine recently alerted me to an issue he has had since upgrading from 9.0.1 to 9.1, and I wondered if anyone else has experienced similar issues or if there is a solution to it?
Basically with Platespin Migrate 9.0.1 he was able to capture images from servers that were not running .NET framework 2.0 (Plate Spin warned him that .NET 2.0 or above was not installed) but the warning was yellow and it allowed him to continue.
But now with version 9.1, the same error message comes up (no surprise there) but it is now a red warning which means he cannot continue with the migration.
He had to reinstall 9.0.1 to continue his migrations which was not ideal.
Yes I would like to use the latest versions of the software I use – but not if it makes my life more difficult 😉
I am considering using Migrate for a large migration project and to be honest I am not looking to do a pre migration project to upgrade .NET on the servers that I am trying to migrate.
Has anyone had experience of this problem and is there a workaround available?