
Solved!
Go to SolutionI
IanFlanagan
1 Rookie
•
4 Posts
0
46948
December 19th, 2016 00:00
Changing VxRail internal components are not currently supported
In the EMC Support article – 000474897 named
VxRail: Changing VxRail internal components are not currently supported.
- Datacenter names,
- Datastore names,
- Cluster names,
- Networks (port groups, vmkernel ports, vDS, network teaming, VLAN ID’s, all other properties)
- Resource Pools
- Templates
- Service VM’s (vCenter, PSC, VxRail Manager, ESRS, Log Insight)
Updated on Nov 14th, the article indicates VxRail 3.0 and 3.5 … are they still ‘locked’ from a VxRail 4.0 perspective??
When are these currently static / hard-coded items going to be made variable for customer selection??
Responses (5)
Solutions (0)
ColinGallagher
90 Posts
5940
1
Posted December 19th, 2016 05:00
Yes no change in 4.0, they cannot be altered. We are looking at making more software components changeable in future releases.
Colin
Reply echolaughmk
2 Intern
•
522 Posts
5940
0
Posted July 18th, 2017 17:00
Hi Colin - any update to this on the roadmap for the latest updates? This is a bit limiting for customers and wasn't sure if this might be closer to being lifted.
thanks!
Reply Nick-name_are_mandatory-Why
1 Message
5125
0
Posted September 11th, 2019 10:00
how do i find SolVe?
Reply

Menno
2 Intern
•
29 Posts
5940
1
Posted July 26th, 2017 03:00
If you go to SolVe, in the "how to" section... you can now select some procedures to change things...
rename:
datacenter, VM folder, VxRail Datastore, VxRail cluster, VxRail VMname and more... have a look.
rgds, Menno