Blog Entry

(View Disclaimer)

We've got some new PlateSpin Protect training coming just around the corner. I mentioned not too long ago that this course was in development. Well now it's in the final stages of operations, where the artwork is done, the covers are printed, the DVDs are burned, and the shrink wrap machine is getting warmed up. I'm talking about "Workload Management Administration with PlateSpin Protect," Course 8017. By the end of this month, you'll be able to buy this course for self-study or sign up to take the class at a Novell Training Partner.

Why am I writing about the coming of this course 2 weeks in advance? Why am I not waiting until it's shipping before I start making noise about it? Because I've got something to show you.

My team has posted a handful-and-a-half (that's 7), hands-on lab demonstrations to the Novell Learning YouTube channel. These are recorded demos of just a small number of the labs that are in Course 8017. And I think they're all on useful topics that are worth taking the time to look at. They're short (all between 4 and 7 minutes) and they cover topics that can help you get started using PlateSpin Protect.

Here are the titles of the demos:

• Preparing the Server for PlateSpin Protect
• Installing PlateSpin Protect
• Licensing PlateSpin Protect
• Adding a VM Container in PlateSpin Protect
• Adding an Image Container in PlateSpin Protect
• Creating Security Groups in PlateSpin Protect
• Creating a Custom Protection Tier in PlateSpin Protect

Just go to http://www.youtube.com/novelllearning and search for PlateSpin.

Of course, I'm hoping to generate interest in the full course when it comes out. So, I'll be blogging about it again later. But for now, I hope PlateSpin Protect customers will get some useful information from these videos that we've posted on YouTube.

Please follow us:
http://twitter.com/novell_training
http://www.facebook.com/NovellTraining

Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).

It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.