Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hello, I have a customer who is upgrading from 11.5 PCCE 2k to 12 and wants to go to a 4k deployment once they are upgraded. My question is if this is supported to change the deployment type without breaking the existing configuration from the 2k de...
The workaround and doc updates for this bug fix do not address all the questions in the bug. It does not give the required settings for autogrowth settings and the doc still shows 10% which is not possible in SQL 2017.
I spoke with the Cisco TAC engineer who spoke specifically about his conversation with the BU and he confirmed in an email. Though, the BU contact is never mentioned by name. I think it would be short-sighted not to support or not to have tested a PC...
In your method did you just add the new components with the inventory tool once they were online? In a conversation with the TAC engineer, I believe the response is actually that it isn't a tested migration. Which makes it one of those "It will proba...
I opened a TAC case on this since there was no supporting documentation. The TAC response (and BU response) is that this is not a supported migration. "Migration from PCCE 2k to 4k or 12k is not supported, you can migrate from PCCE 2k to UCCE 4k o...
So, its just a matter of rerunning the set deployment after we get to version 12 and then using the inventory tools to add the extra components? Sounds straight forward enough. I was just wondering if there was a white paper or tech reference doc t...
