K2000 3.5 Horror/Success stories?
I am planning for the 3.5 update, and am interested if anybody has any horror and/or success stories to share.
Answers (5)
I wouldn't call it a horror story, but my update had to be helped along by support. Also, they didn't document that it would take away the ability to capture images to the RSA, which was a feature of the KNIT. They said it was an unintentional bug that was fixed...
i'm still working through a few reports of errors, not sure exactly what is causing them.
Success here. As I've never had either my K2 or my K1 pull down an automatic upgrade, I downloaded the packages myself and ran them just last week. I was a bit leary since the 5.4 K1 upgrade required alot of support intervention, but this time everything ran through flawlessly on both boxes.
Success for me. The update was smooth and so far I haven't experienced any problems while using the box. Though I'm probably jinxing myself by saying that. :)
Just finished ours no problems so far. The RSA's sync'd out also without a hitch. Current wim deployments stored on windows shares still work. Now onto testing uploading a new mac netboot and uploading new wim file for an image
Comments:
-
Hey SMal, can you build new KBEs with the KBE Manipulator? I'm getting hung up cuz it won't fill in the password... - nheyne 11 years ago
-
KBEM won't work with the 3.5 Media Manager until Corey gets a chance to update it. Your 3.4 custom KBEs should still work just fine with 3.5 if that's what you are concerned about. - mpace 11 years ago
Been running stable for a few weeks now. One thing to be aware of before you update is that 3.5 no longer supports 32-bit versions of the K2000. If you have a 32-bit virtual K2000 you can follow these steps to upgrade it: http://www.kace.com/uk/support/resources/kb/article/K2000-upgrade-35-32bit-support
If you have a virtual appliance, it's always a good idea to take a snapshot prior to updating.
