Get Device Configuration Script
Updated: June 7, 2012
The Get Device Configuration Script operation returns a script that you can use to configure local VPN devices to connect to the gateway.
Request
The Get Device Configuration Script request may be constructed as follows. Replace <subscription-id> with the name of your subscription ID, and <virtual-network-name> with the name of the virtual network associated with the gateway.
| Method | Request URI | HTTP Version |
|---|---|---|
|
GET |
|
HTTP/1.1 |
URI Parameters
| URI Parameter | Description |
|---|---|
|
vendor |
Required. Specifies the vendor of the on-premise VPN device. |
|
platform |
Required. Specifies the platform of the on-premise VPN device. |
|
OSfamily |
Required. Specifies the operating system family of the on-premise VPN device. |
Request Headers
The following table describes the request headers.
| Request Header | Description |
|---|---|
|
x-ms-version |
Required. Specifies the version of the operation to use for this request. For more information, see Versioning for the Blob, Queue, and Table services in Windows Azure. |
Request Body
None.
Response
The response includes an HTTP status code, a response body, and a set of response headers.
Status Code
A successful operation returns status code 200 (OK). For information about status codes, see Service Management Status and Error Codes.
Response Headers
The response for this operation includes the following headers. The response may also include additional standard HTTP headers. All standard headers conform to the HTTP/1.1 protocol specification.
| Response Header | Description |
|---|---|
|
x-ms-request-id |
This header uniquely identifies the request that was made and can be used for troubleshooting the request. For more information, see Troubleshooting API Operations. |
Response Body
The response body contains the device configuration script as a text string that you can use to configure a VPN device.
Authorization
Any management certificate associated with the subscription specified by <subscription-id> can be used to authenticate this operation. For additional details, see Authenticating Service Management Requests.
Remarks
None.
See Also