I'm little bit confused here, but am I the only one who is getting the old 6.0up90 5845 instead of the latest 6.0up95 b6156 by following the download links? Sure, I can use the ftp server directly but ...
I'm little bit confused here, but am I the only one who is getting the old 6.0up90 5845 instead of the latest 6.0up95 b6156 by following the download links? Sure, I can use the ftp server directly but ...
b_6156 has been temporarily removed from the downloads. It will be back soon.
Currently, b_5845 should be used.
Ok now thats getting more suspicious and confusing. Wouldn't that normally be a simple update? Instead of blocking silently an already announced version?
You should correct the link to the release notes. It shows the up95 b6156 version instead of up90 b5845.
For me it dosen't matter when what version will be or not released, I don't care. I'm just wondering about your release and information practice which I've to explain to my team leader while he is asking me why I didn't do the scheduled update. That's all.
What if we already have installed 6156?
6.0up95.8101.6156 64bit
Is this going to be a problem?
Last edited by webguyz; 05-22-2012 at 12:01 AM. Reason: spelling
If you are using b6156 and it's working properly for you, then it's to keep it running.
We discovered some storage availability issues in ESX when updating from older DSS V6 versions.
If you have used an older DSS V6 version and after the update to b6156 you are facing some problems, you should downgrade to the older version to fix it.
If you made a clean install of the DSS V6 b6156 and you are facing any problems with storage availability in ESX downgrading to the older version won't help.
BR,
Tomek
So no worries as long as we are not use ESX. Good to know. Thanks!