VMware VS4-ENT-PL-A Setup Guide - Page 51

How vCenter Single Sign-On Affects vCenter Server Installation, Database Prerequisites, Simple Install - planned

Page 51 highlights

Chapter 3 Before You Install vCenter Server Database Prerequisites n Verify that your vCenter Server database meets the database requirements. See "vCenter Server Database Configuration Notes," on page 30 and "Preparing vCenter Server Databases," on page 30. n Create a vCenter Server database, unless you plan to install the bundled database. How vCenter Single Sign-On Affects vCenter Server Installation Starting with version 5.1, vSphere includes a vCenter Single Sign-On component as part of the vCenter Server management infrastructure. This change affects vCenter Server installation. Authentication by vCenter Single Sign-On makes the VMware cloud infrastructure platform more secure by allowing the vSphere software components to communicate with each other through a secure token exchange mechanism. For information about configuring vCenter Single Sign-On, see vSphere Security. For more information about vCenter Single Sign-On deployment modes, see "vCenter Single Sign-On Deployment Modes," on page 52. For the first installation of vCenter Server, you must install all components. In subsequent installations in the same environment, or if you add services, you do not have to install vCenter Single Sign-On. One vCenter Single Sign-On server can serve your entire vSphere environment. After you install vCenter Single Sign-On once, you can connect all new vCenter Server instances to the same vCenter Single Sign-On service. You must install an Inventory Service instance for each vCenter Server instance. Simple Install The Simple Install option installs vCenter Single Sign-On, the vSphere Web Client, vCenter Inventory Service, and vCenter Server on the same host or virtual machine. Simple Install is appropriate for most deployments. Custom Install If you want to customize the location and setup of each component, you can install the components separately by performing a custom install and selecting the individual installation options, in the following order: 1 vCenter Single Sign-On 2 vSphere Web Client 3 vCenter Inventory Service 4 vCenter Server You can install each component on a different host or virtual machine. If you decide on installing multiple vCenter Server systems, you can point to the same vCenter Single SignOn service for each vCenter Server. Installing in Multiple Locations Unlike vCenter Single Sign-On version 5.1, vCenter Single Sign-On 5.5 synchronizes authentication data across locations. If you install vCenter Server systems in multiple locations, you can install a vCenter Single Sign-On server in each location. When you install the second and subsequent instances of vCenter Single Sign-On, you can point it to the first vCenter Single Sign-On instance during installation. The two instances synchronize their VMware Directory Service instances. Changes to one instance are propagated to the other instance. VMware, Inc. 51

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276

Database Prerequisites
n
Verify that your vCenter Server database meets the database requirements. See
“vCenter Server
Database Configuration Notes,”
on page 30 and
“Preparing vCenter Server Databases,”
on page 30.
n
Create a vCenter Server database, unless you plan to install the bundled database.
How vCenter Single Sign-On Affects vCenter Server Installation
Starting with version 5.1, vSphere includes a vCenter Single Sign-On component as part of the
vCenter Server management infrastructure. This change affects vCenter Server installation.
Authentication by vCenter Single Sign-On makes the VMware cloud infrastructure platform more secure by
allowing the vSphere software components to communicate with each other through a secure token
exchange mechanism.
For information about configuring vCenter Single Sign-On, see
vSphere Security
. For more information about
vCenter Single Sign-On deployment modes, see
“vCenter Single Sign-On Deployment Modes,”
on
page 52.
For the first installation of vCenter Server, you must install all components. In subsequent installations in
the same environment, or if you add services, you do not have to install vCenter Single Sign-On. One
vCenter Single Sign-On server can serve your entire vSphere environment. After you install vCenter Single
Sign-On once, you can connect all new vCenter Server instances to the same vCenter Single Sign-On service.
You must install an Inventory Service instance for each vCenter Server instance.
Simple Install
The Simple Install option installs vCenter Single Sign-On, the vSphere Web Client, vCenter Inventory
Service, and vCenter Server on the same host or virtual machine. Simple Install is appropriate for most
deployments.
Custom Install
If you want to customize the location and setup of each component, you can install the components
separately by performing a custom install and selecting the individual installation options, in the following
order:
1
vCenter Single Sign-On
2
vSphere Web Client
3
vCenter Inventory Service
4
vCenter Server
You can install each component on a different host or virtual machine.
If you decide on installing multiple vCenter Server systems, you can point to the same vCenter Single Sign-
On service for each vCenter Server.
Installing in Multiple Locations
Unlike vCenter Single Sign-On version 5.1, vCenter Single Sign-On 5.5 synchronizes authentication data
across locations.
If you install vCenter Server systems in multiple locations, you can install a vCenter Single Sign-On server
in each location. When you install the second and subsequent instances of vCenter Single Sign-On, you can
point it to the first vCenter Single Sign-On instance during installation. The two instances synchronize their
VMware Directory Service instances. Changes to one instance are propagated to the other instance.
Chapter 3 Before You Install vCenter Server
VMware, Inc.
51