Proxy Configuration Manual For Mac

This document covers the configuration language as implemented in the version specified above. It does not provide any hint, example or advice. For such documentation, please refer to the Reference Manual or the Architecture Manual. The summary below is meant to help you search sections by name and navigate through the document. Note to documentation contributors: This document is formatted with 80 columns per line, with even number of spaces for indentation and without tabs.

1. Quicken 2017 Manual For Mac
2. Hp Deskjet 2540 Manual For Mac
3. Embrilliance Essentials Manual For Mac

Manual Configuration For MacOS With OpenVPN Your FoxyProxy accounts come with both VPN and proxy service. These instructions explain how to connect to your VPN accounts using a method called OpenVPN. Follow these instructions to configure Google Chrome to use a proxy server. You will receive the IP Address and Port Number of your Proxy Server(s) in a.

Please follow these rules strictly so that it remains easily printable everywhere. If a line needs to be printed verbatim and does not fit, please end each line with a backslash (' ') and continue on next line, indented by two characters. It is also sometimes useful to prefix all output lines (logs, console outs) with 3 closing angle brackets (') in order to help get the difference between inputs and outputs when it can become ambiguous.

If you add sections, please update the summary below for easier searching. The HTTP protocol is transaction-driven.

This means that each request will lead to one and only one response. Traditionally, a TCP connection is established from the client to the server, a request is sent by the client on the connection, the server responds and the connection is closed. A new request will involve a new connection: CON1 REQ1. RESP1 CLO1 CON2 REQ2.

RESP2 CLO2. In this mode, called the 'HTTP close' mode, there are as many connection establishments as there are HTTP transactions. Since the connection is closed by the server after the response, the client does not need to know the content length. Due to the transactional nature of the protocol, it was possible to improve it to avoid closing a connection between two subsequent transactions. In this mode however, it is mandatory that the server indicates the content length for each response so that the client does not wait indefinitely. For this, a special header is used: 'Content-length'.

This mode is called the 'keep-alive' mode: CON REQ1. RESP1 REQ2. RESP2 CLO. Its advantages are a reduced latency between transactions, and less processing power required on the server side. It is generally better than the close mode, but not always because the clients often limit their concurrent connections to a smaller value. A last improvement in the communications is the pipelining mode.

It still uses keep-alive, but the client does not wait for the first response to send the second request. This is useful for fetching large number of images composing a page: CON REQ1 REQ2. RESP1 RESP2 CLO. This can obviously have a tremendous benefit on performance because the network latency is eliminated between subsequent requests. Many HTTP agents do not correctly support pipelining since there is no way to associate a response with the corresponding request in HTTP. For this reason, it is mandatory for the server to reply in the exact same order as the requests were received. By default HAProxy operates in keep-alive mode with regards to persistent connections: for each connection it processes each request and response, and leaves the connection idle on both sides between the end of a response and the start of a new request.

HAProxy supports 5 connection modes: - keep alive: all requests and responses are processed (default) - tunnel: only the first request and response are processed, everything else is forwarded with no analysis. passive close: tunnel with 'Connection: close' added in both directions. server close: the server-facing connection is closed after the response. forced close: the connection is actively closed after end of response. HTTP request. Line 1 is the 'request line'.

It is always composed of 3 fields: - a METHOD: GET - a URI: /serv/login.php?lang=en&profile=2 - a version tag: HTTP/1.1 All of them are delimited by what the standard calls LWS (linear white spaces), which are commonly spaces, but can also be tabs or line feeds/carriage returns followed by spaces/tabs. The method itself cannot contain any colon (':') and is limited to alphabetic letters. All those various combinations make it desirable that HAProxy performs the splitting itself rather than leaving it to the user to write a complex or inaccurate regular expression. The URI itself can have several forms: - A 'relative URI': /serv/login.php?lang=en&profile=2 It is a complete URL without the host part. This is generally what is received by servers, reverse proxies and transparent proxies. An 'absolute URI', also called a 'URL': It is composed of a 'scheme' (the protocol name followed by '://'), a host name or address, optionally a colon (':') followed by a port number, then a relative URI beginning at the first slash ('/') after the address part. This is generally what proxies receive, but a server supporting HTTP/1.1 must accept this form too.

a star ('.' ): this form is only accepted in association with the OPTIONS method and is not relayable. It is used to inquiry a next hop's capabilities. an address:port combination: 192.168.0.12:80 This is used with the CONNECT method, which is used to establish TCP tunnels through HTTP proxies, generally for HTTPS, but sometimes for other protocols too. In a relative URI, two sub-parts are identified. The part before the question mark is called the '. It is typically the relative path to static objects on the server.

The part after the question mark is called the 'query string'. It is mostly used with GET requests sent to dynamic scripts and is very specific to the language, framework or application in use. The request headers. The headers start at the second line. They are composed of a name at the beginning of the line, immediately followed by a colon (':').

Traditionally, an LWS is added after the colon but that's not required. Then come the values. Multiple identical headers may be folded into one single line, delimiting the values with commas, provided that their order is respected. This is commonly encountered in the 'Cookie:' field. A header may span over multiple lines if the subsequent lines begin with an LWS. In the example in 1.2, lines 4 and 5 define a total of 3 values for the 'Accept:' header. Contrary to a common mis-conception, header names are not case-sensitive, and their values are not either if they refer to other header names (such as the 'Connection:' header).

The end of the headers is indicated by the first empty line. People often say that it's a double line feed, which is not exact, even if a double line feed is one valid form of empty line.

Fortunately, HAProxy takes care of all these complex combinations when indexing headers, checking values and counting them, so there is no reason to worry about the way they could be written, but it is important not to accuse an application of being buggy if it does unusual, valid things. Important note: As suggested by RFC2616, HAProxy normalizes headers by replacing line breaks in the middle of headers by LWS in order to join multi-line headers.

This is necessary for proper analysis and helps less capable HTTP parsers to work correctly and not to be fooled by such complex constructs. HTTP response. An HTTP response looks very much like an HTTP request. Both are called HTTP messages. Let's consider this HTTP response: Line Contents number 1 HTTP/1.1 200 OK 2 Content-length: 350 3 Content-Type: text/html As a special case, HTTP supports so called 'Informational responses' as status codes 1xx. These messages are special in that they don't convey any part of the response, they're just used as sort of a signaling message to ask a client to continue to post its request for instance. In the case of a status 100 response the requested information will be carried by the next non-100 response message following the informational one.

This implies that multiple responses may be sent to a single request, and that this only works when keep-alive is enabled (1xx messages are HTTP/1.1 only). HAProxy handles these messages and is able to correctly forward and skip them, and only process the next non-100 response. As such, these messages are neither logged nor transformed, unless explicitly state otherwise.

Status 101 messages indicate that the protocol is changing over the same connection and that haproxy must switch to tunnel mode, just as if a CONNECT had occurred. Then the Upgrade header would contain additional information about the type of protocol the connection is switching to. The Response line.

Line 1 is the 'response line'. It is always composed of 3 fields: - a version tag: HTTP/1.1 - a status code: 200 - a reason: OK The status code is always 3-digit. The first digit indicates a general status: - 1xx = informational message to be skipped (eg: 100, 101) - 2xx = OK, content is following (eg: 200, 206) - 3xx = OK, no content following (eg: 302, 304) - 4xx = error caused by the client (eg: 401, 403, 404) - 5xx = error caused by the server (eg: 500, 502, 503) Please refer to RFC2616 for the detailed meaning of all such codes.

The 'reason' field is just a hint, but is not parsed by clients. Anything can be found there, but it's a common practice to respect the well-established messages. It can be composed of one or multiple words, such as 'OK', 'Found', or 'Authentication Required'. HAProxy's configuration process involves 3 major sources of parameters: - the arguments from the command-line, which always take precedence - the 'global' section, which sets process-wide parameters - the proxies sections which can take form of 'defaults', 'listen', 'frontend' and 'backend'. The configuration file syntax consists in lines beginning with a keyword referenced in this manual, optionally followed by one or several parameters delimited by spaces. If spaces have to be entered in strings, then they must be preceded by a backslash (' ') to be escaped.

Backslashes also have to be escaped by doubling them. Some parameters involve values representing time, such as timeouts. These values are generally expressed in milliseconds (unless explicitly stated otherwise) but may be expressed in any other unit by suffixing the unit to the numeric value.

It is important to consider this because it will not be repeated for every keyword. Supported units are: - us: microseconds. 1 microsecond = 1/1000000 second - ms: milliseconds. 1 millisecond = 1/1000 second. This is the default. s: seconds.

1s = 1000ms - m: minutes. 1m = 60s = 60000ms - h: hours. 1h = 60m = 3600s = 3600000ms - d: days. 1d = 24h = 1440m = 86400s = 86400000ms Examples. # Simple configuration for an HTTP proxy listening on port 80 on all # interfaces and forwarding requests to a single backend 'servers' with a # single server 'server1' listening on 127.0.0.1:8000 global daemon maxconn 256 defaults mode http timeout connect 5000ms timeout client 50000ms timeout server 50000ms frontend http-in bind.:80 defaultbackend servers backend servers server server1 127.0.0.1:8000 maxconn 32 # The same configuration defined with a single listen block. Shorter but # less expressive, especially in HTTP mode.

Quicken 2017 Manual For Mac

Global daemon maxconn 256 defaults mode http timeout connect 5000ms timeout client 50000ms timeout server 50000ms listen http-in bind.:80 server server1 127.0.0.1:8000 maxconn 32 Assuming haproxy is in $PATH, test these configurations in a shell with: $ sudo haproxy -f configuration.conf -c. On Linux 2.6 and above, it is possible to bind a process to a specific CPU set. This means that the process will never run on other CPUs. The ' directive specifies CPU sets for process sets. The first argument is the process number to bind.

This process must have a number between 1 and 32 or 64, depending on the machine's word size, and any process IDs above nbproc are ignored. It is possible to specify all processes at once using 'all', only odd numbers using 'odd' or even numbers using 'even', just like with the ' directive. The second and forthcoming arguments are CPU sets. Each CPU set is either a unique number between 0 and 31 or 63 or a range with two such numbers delimited by a dash ('-'). Multiple CPU numbers or ranges may be specified, and the processes will be allowed to bind to all of them. Obviously, multiple ' directives may be specified. Each ' directive will replace the previous ones when they overlap.

Changes the process' group ID to. It is recommended that the group ID is dedicated to HAProxy or to a small set of similar daemons. HAProxy must be started with a user belonging to this group, or with superuser privileges. Note that if haproxy is started from a user having supplementary groups, it will only be able to drop these groups if started with superuser privileges. See also '.

This keyword is available in sections:. ' and '. This keyword is available in sections:. '. all odd even -. Limits the stats socket to a certain set of processes numbers.

By default the stats socket is bound to all processes, causing a warning to be emitted when nbproc is greater than 1 because there is no way to select the target process when connecting. However, by using this setting, it becomes possible to pin the stats socket to a specific set of processes, typically the first one. The warning will automatically be disabled when this setting is used, whatever the number of processes used. The maximum process ID depends on the machine's word size (32 or 64). A better option consists in using the ' setting of the ' line to force the process on each line.

prefix mode user uid group gid Fixes common settings to UNIX listening sockets declared in ' statements. This is mainly used to simplify declaration of those UNIX sockets and reduce the risk of errors, since those settings are most commonly required but are also process-specific. The setting can be used to force all socket path to be relative to that directory. This might be needed to access another component's chroot.

Note that those paths are resolved before haproxy chroots itself, so they are absolute. The, and all have the same meaning as their homonyms used by the ' statement. If both are specified, the ' statement has priority, meaning that the ' settings may be seen as process-wide default settings. By default, haproxy tries to spread the start of health checks across the smallest health check interval of all the servers in a farm.

The principle is to avoid hammering services running on the same server. But when using large check intervals (10 seconds or more), the last servers in the farm take some time before starting to be tested, which can be a problem. This parameter is used to enforce an upper bound on delay between the first and the last check, even if the servers' check intervals are larger.

When servers run with shorter intervals, their intervals will be respected though. Sets the maximum per-process number of concurrent connections to. It is equivalent to the command-line argument '-n'.

Proxies will stop accepting connections when this limit is reached. The ' parameter is automatically adjusted according to this value. Note: the 'select' poller cannot reliably use more than 1024 file descriptors on some platforms. If your platform only supports select and reports 'select FAILED' on startup, you need to reduce maxconn until it works (slightly below 500 in general). Sets the maximum per-process number of connections per second to. Proxies will stop accepting connections when this limit is reached. It can be used to limit the global capacity regardless of each frontend capacity.

It is important to note that this can only be used as a service protection measure, as there will not necessarily be a fair share between frontends when the limit is reached, so it's a good idea to also limit each frontend to some value close to its expected share. Also, lowering tune.maxaccept can improve fairness. Sets the maximum CPU usage HAProxy can reach before stopping the compression for new requests or decreasing the compression level of current requests. It works like 'maxcomprate' but measures CPU usage instead of incoming data bandwidth. The value is expressed in percent of the CPU used by haproxy. In case of multiple processes (nbproc 1), each process manages its individual usage.

A value of 100 disable the limit. The default value is 100. Setting a lower value will prevent the compression work from slowing the whole process down and from introducing high latencies. Sets the maximum per-process number of sessions per second to. Proxies will stop accepting connections when this limit is reached. It can be used to limit the global capacity regardless of each frontend capacity. It is important to note that this can only be used as a service protection measure, as there will not necessarily be a fair share between frontends when the limit is reached, so it's a good idea to also limit each frontend to some value close to its expected share.

Also, lowering tune.maxaccept can improve fairness. Sets the maximum per-process number of concurrent SSL connections to. By default there is no SSL-specific limit, which means that the global maxconn setting will apply to all connections.

Setting this limit avoids having openssl use too much memory and crash when malloc returns NULL (since it unfortunately does not reliably check for such conditions). Note that the limit applies both to incoming and outgoing connections, so one connection which is deciphered then ciphered accounts for 2 SSL connections. Sets the maximum per-process number of SSL sessions per second to.

SSL listeners will stop accepting connections when this limit is reached. It can be used to limit the global SSL CPU usage regardless of each frontend capacity. It is important to note that this can only be used as a service protection measure, as there will not necessarily be a fair share between frontends when the limit is reached, so it's a good idea to also limit each frontend to some value close to its expected share. It is also important to note that the sessions are accounted before they enter the SSL stack and not after, which also protects the stack against bad handshakes. Also, lowering tune.maxaccept can improve fairness. Sets the buffer size to this size (in bytes). Lower values allow more sessions to coexist in the same amount of RAM, and higher values allow some applications with very large cookies to work.

The default value is 16384 and can be changed at build time. It is strongly recommended not to change this from the default value, as very low values will break some services such as statistics, and values larger than default size will increase memory usage, possibly causing the system to run out of memory. At least the global maxconn parameter should be decreased by the same factor as this one is increased. If HTTP request is larger than (tune.bufsize - tune.maxrewrite), haproxy will return HTTP 400 (Bad Request) error.

Similarly if an HTTP response is larger than this size, haproxy will return HTTP 502 (Bad Gateway). Sets the maximum length of captured cookies.

This is the maximum value that the 'capture cookie xxx len yyy' will be allowed to take, and any upper value will automatically be truncated to this one. It is important not to set too high a value because all cookie captures still allocate this size whatever their configured value (they share a same pool). This value is per request per response, so the memory allocated is twice this value per connection. When not specified, the limit is set to 63 characters.

It is recommended not to change this value. Sets the maximum number of headers in a request. When a request comes with a number of headers greater than this value (including the first line), it is rejected with a '400 Bad Request' status code. Similarly, too large responses are blocked with '502 Bad Gateway'. The default value is 101, which is enough for all usages, considering that the widely deployed Apache server uses the same limit. It can be useful to push this limit further to temporarily allow a buggy application to work by the time it gets fixed. Keep in mind that each new header consumes 32bits of memory for each session, so don't push this limit too high.

Sets the duration after which haproxy will consider that an empty buffer is probably associated with an idle stream. This is used to optimally adjust some packet sizes while forwarding large and small data alternatively.

The decision to use splice or to send large buffers in SSL is modulated by this parameter. The value is in milliseconds between 0 and 65535. A value of zero means that haproxy will not try to detect idle streams. The default is 1000, which seems to correctly detect end user pauses (eg: read a page before clicking). There should be not reason for changing this value.

Please check tune.ssl.maxrecord below. Sets the maximum number of consecutive connections a process may accept in a row before switching to other work. In single process mode, higher numbers give better performance at high connection rates. However in multi-process modes, keeping a bit of fairness between processes generally is better to increase performance. This value applies individually to each listener, so that the number of processes a listener is bound to is taken into account. This value defaults to 64.

In multi-process mode, it is divided by twice the number of processes the listener is bound to. Setting this value to -1 completely disables the limitation. It should normally not be needed to tweak this value. Sets the reserved buffer space to this size in bytes. The reserved space is used for header rewriting or appending. The first reads on sockets will never fill more than bufsize-maxrewrite. Historically it has defaulted to half of bufsize, though that does not make much sense since there are rarely large numbers of headers to add.

Setting it too high prevents processing of large requests or responses. Setting it too low prevents addition of new headers to already large requests or to POST requests.

It is generally wise to set it to about 1024. It is automatically readjusted to half of bufsize if it is larger than that. This means you don't have to worry about it when changing bufsize. Forces the kernel socket receive buffer size on the client or the server side to the specified value in bytes.

This value applies to all TCP/HTTP frontends and backends. It should normally never be set, and the default size (0) lets the kernel autotune this value depending on the amount of available memory. However it can sometimes help to set it to very low values (eg: 4096) in order to save kernel memory by preventing it from buffering too large amounts of received data.

Lower values will significantly increase CPU usage though. Forces the kernel socket send buffer size on the client or the server side to the specified value in bytes. This value applies to all TCP/HTTP frontends and backends. It should normally never be set, and the default size (0) lets the kernel autotune this value depending on the amount of available memory. However it can sometimes help to set it to very low values (eg: 4096) in order to save kernel memory by preventing it from buffering too large amounts of received data.

Lower values will significantly increase CPU usage though. Another use case is to prevent write timeouts with extremely slow clients due to the kernel waiting for a large part of the buffer to be read before notifying haproxy again. Sets the size of the global SSL session cache, in a number of blocks. A block is large enough to contain an encoded session without peer certificate. An encoded session with peer certificate is stored in multiple blocks depending on the size of the peer certificate. A block uses approximately 200 bytes of memory. The default value may be forced at build time, otherwise defaults to 20000.

When the cache is full, the most idle entries are purged and reassigned. Higher values reduce the occurrence of such a purge, hence the number of CPU-intensive SSL handshakes by ensuring that all users keep their session as long as possible. All entries are pre-allocated upon startup and are shared between all processes if '. This keyword is available in sections:. ' is greater than 1.

Setting this value to 0 disables the SSL session cache. Sets the maximum amount of bytes passed to SSLwrite at a time.

Default value 0 means there is no limit. Over SSL/TLS, the client can decipher the data only once it has received a full record. With large records, it means that clients might have to download up to 16kB of data before starting to process them.

Limiting the value can improve page load times on browsers located over high latency or low bandwidth networks. It is suggested to find optimal values which fit into 1 or 2 TCP segments (generally 1448 bytes over Ethernet with TCP timestamps enabled, or 1460 when timestamps are disabled), keeping in mind that SSL/TLS add some overhead. Typical values of 1419 and 2859 gave good results during tests. Use 'strace -e trace=write' to find the best value. Haproxy will automatically switch to this setting after an idle stream has been detected (see tune.idletimer above). Sets the maximum size of the Diffie-Hellman parameters used for generating the ephemeral/temporary Diffie-Hellman key in case of DHE key exchange.

The final size will try to match the size of the server's RSA (or DSA) key (e.g, a 2048 bits temporary DH key for a 2048 bits RSA key), but will not exceed this maximum value. Default value if 1024. Only 1024 or higher values are allowed. Higher values will increase the CPU load, and values greater than 1024 bits are not supported by Java 7 and earlier clients. This value is not used if static Diffie-Hellman parameters are supplied via the certificate file. It is possible to synchronize server entries in stick tables between several haproxy instances over TCP connections in a multi-master fashion. Each instance pushes its local updates and insertions to remote peers.

Server IDs are used to identify servers remotely, so it is important that configurations look similar or at least that the same IDs are forced on each server on all participants. Interrupted exchanges are automatically detected and recovered from the last known point. In addition, during a soft restart, the old process connects to the new one using such a TCP connection to push all its entries before the new process tries to connect to other peers. That ensures very fast replication during a reload, it typically takes a fraction of a second even for large tables. Proxy configuration can be located in a set of sections: - defaults - frontend - backend - listen A 'defaults' section sets default parameters for all other sections following its declaration. Those default parameters are reset by the next 'defaults' section. See below for the list of parameters which can be set in a 'defaults' section.

The name is optional but its use is encouraged for better readability. A 'frontend' section describes a set of listening sockets accepting client connections. A 'backend' section describes a set of servers to which the proxy will connect to forward incoming connections. A 'listen' section defines a complete proxy with its frontend and backend parts combined in one section. It is generally useful for TCP-only traffic.

All proxy names must be formed from upper and lower case letters, digits, '-' (dash), ' (underscore), '.' (dot) and ':' (colon).

ACL names are case-sensitive, which means that 'www' and 'WWW' are two different proxies. Historically, all proxy names could overlap, it just caused troubles in the logs. Since the introduction of content switching, it is mandatory that two proxies with overlapping capabilities (frontend/backend) have different names. However, it is still permitted that a frontend and a backend share the same name, as this configuration seems to be commonly encountered. Right now, two major proxy modes are supported: 'tcp', also known as layer 4, and 'http', also known as layer 7. In layer 4 mode, HAProxy simply forwards bidirectional traffic between two sides.

In layer 7 mode, HAProxy analyzes the protocol, and can interact with it by allowing, blocking, switching, adding, modifying, or removing arbitrary contents in requests or responses, based on arbitrary criteria. In HTTP mode, the processing applied to requests and responses flowing over a connection depends in the combination of the frontend's HTTP options and the backend's.

HAProxy supports 5 connection modes: - KAL: keep alive (') which is the default mode: all requests and responses are processed, and connections remain open but idle between responses and new requests. TUN: tunnel ('): this was the default mode for versions 1.0 to 1.5-dev21: only the first request and response are processed, and everything else is forwarded with no analysis at all.

This mode should not be used as it creates lots of trouble with logging and HTTP processing. PCL: passive close ('): exactly the same as tunnel mode, but with 'Connection: close' appended in both directions to try to make both ends close after the first request/response exchange. SCL: server close ('): the server-facing connection is closed after the end of the response is received, but the client-facing connection remains open. FCL: forced close ('): the connection is actively closed after the end of the response.

The effective mode that will be applied to a connection passing through a frontend and a backend can be determined by both proxy modes according to the following matrix, but in short, the modes are symmetric, keep-alive is the weakest option and force close is the strongest. Backend mode KAL TUN PCL SCL FCL -+-+-+-+-+- KAL KAL TUN PCL SCL FCL -+-+-+-+-+- TUN TUN TUN PCL SCL FCL Frontend -+-+-+-+-+- mode PCL PCL PCL PCL FCL FCL -+-+-+-+-+- SCL SCL SCL FCL SCL FCL -+-+-+-+-+- FCL FCL FCL FCL FCL FCL Proxy keywords matrix. The following list of keywords is supported. Most of them may only be used in a limited set of section types.

Some of them are marked as 'deprecated' because they are inherited from an old syntax which may be confusing or functionally limited, and there are new recommended keywords to replace them. Keywords marked with '(.)' can be optionally inverted using the 'no' prefix, eg. 'no option contstats'. This makes sense when the option has been enabled by default and must be disabled for a specific instance. Such options may also be prefixed with 'default' in order to restore default settings regardless of what has been specified in a previous 'defaults' section.

Keyword defaults frontend listen backend keyword defaults frontend listen backend.

In of the series on Parallels Mac Management for SCCM, I talked about installing the Parallels Console Extensions into your environment. In Part 2, I will install our first ‘role’ the Parallels Configuration Manager Proxy.

Parallels Mac Management for SCCM requires the installation of the proxy on a server that resides in the defined ConfigMgr boundaries. It is recommended that the SMS Provider is installed on the server that hosts the Parallels Configuration Manager Proxy. If you need assistance on installing the SMS Provider on your remote device then take a look at my on how to do this.

The SMS Provider is not installed then you can point the proxy to a remote SMS Provider during configuration. A proxy should be deployed to a Primary Site, if you have Secondary Sites in your environment then you should also deploy a proxy to each of those to reduced traffic over the link and to simplify Mac Client enrollment. The Parallels Configuration Manager Proxy is a Windows Service application that acts as a proxy been the Mac client and ConfigMgr and can be installed on devices running Windows 2008R2 and later. Pre-Requisites The following pre-requisites need to be installed on the server that will host the proxy:.Net Framework 4.Net Framework 3.5. Visual C 2010 Redist x86 available from. Server patched with the latest updates. For Server 2012 – if not patched then install the following:.

Permissions Needed to run the Installation The account that will install the Parallels Configuration Manager Proxy requires the following rights:. Local Administrator on the server. DCOM Remote Activation permission. Full Admin rights in ConfigMgr. Permissions in AD. Open ADSI Edit by clicking Start Administrative Tools ADSI Edit.

Verify that the following container exists: DC= / DC= / CN=System / CN=ParallelsServices. If the container above doesn’t exist, grant the user the Create All Child Objects and Read permissions on the CN=System container. When granting these permissions to the user, apply it to This object and all descendant objects. If the container exists, do the following:.

Make sure the user have Read, Write, and Create All Child Objects permissions on it. Make sure the user has the Full Control permission on the CN=ParallelsServices / PmaConfigMgrProxy- container. Verify that the DC= / DC= / CN= Program Data / CN=Parallels container exists. If the container above doesn’t exist, grant the user the Create All Child Objects and Read permissions on the CN=Program Data container. When granting these permissions to the user, apply it to This object and all descendant objects. If the CN=Parallels container exists, continue with the following steps. Verify that the CN=Parallels / CN=Parallels Management Suite container exists.

If it doesn’t, grant the user the Create All Child Objects and Read permissions on CN=Parallels container. If the CN=Parallels / CN=Parallels Management Suite container exists, make sure that the user has Read, Write, and Create All Child Objects permissions on it.

Permissions to read/write SPN. SQL Server dbcreator role for the account on the ConfigMgr site database – a DB called PMM will be created. Administrative Rights in Authorization Manager – if Parallels has been previously installed and the Authorization Store exists, then the user configuring the Parallels Proxy must be assigned to the Administrator role in Authorization Manager Installation Note that for the series I am going to install all the Parallels roles on a separate site system server called Parallels.

Add the.Net Framework 3.5 and 4.5 features to your server and install the required Windows Updates. Download the Visual C 2010 Redist x86 and run the install. Accept the licence agreement and click Install.

Click Finish when complete. Run the ‘Parallels Mac Management for SCCM.exe’ installation file and when the wizard appears deselect ‘MDM Server’ and choose ‘Configuration Manager Proxy’. Click Install to begin the installation. Leave the checkbox for ‘Configure Parallels’ ticked and click Finish when complete. At this stage the configuration of the proxy takes place.

If you have installed a local SMS Provider then choose Local Server. I haven’t installed a provider and therefore I am pointing back the SMS Provider on my site server.

Next, an account needs to be assigned to run the Proxy as a Windows Service. The account must be:. A domain user. A local administrator. Have the DCOM Remote Activation permission. Be a full ConfigMgr administrator.

If the CN=System / CN=ParallelsServices / CN=PmaConfigMgrProxy- container exists in Active Directory, the user must have Read, Write, and Create All Child Objects permissions on it. If the container above doesn’t exist, grant the user the Create All Child Objects and Read permissions on the CN=System container.

When granting these permissions to the user, apply it to This object and all descendant objects. Specify an account and click Next. Address any pre-requisite issues that are encountered. Here for example I had to edit the permissions to the inboxes ddm.box on the site server. Once pre-requisites are addressed the check can be Rerun with ‘Rerun’ button and the Next option should become available.

Hp Deskjet 2540 Manual For Mac

As stated in of the series, Parallels can run without the PKI requirements of native ConfigMgr Mac support, although the option to use HTTPS is there. I’ve selected HTTP and then clicked Next. At this point it is possible to configure RBAC for Parallels. I have left this at default.

Embrilliance Essentials Manual For Mac

The configuration wizard can be run again at anytime if changes are needed here. Click Next. Now, the default ports required for communication with the ConfigMgr console and Mac clients can be altered. Decide whether to enroll into the Parallels CEIP program and click Next.

Click Finish on the summary screen. Once complete you’ll be notified that the proxy settings have been updated and that you can run the wizard again at any time via the Start Menu. If you take a look at your ConfigMgr DB you’ll notice that the PMM DB has been created. In your System container in AD the ParallelsServices container,and in the ProgramData container, the Parallels container have been created. That’s all for now. In I’ll be delving deeper into the world of Parallels Mac Management for SCCM by installing the NetBoot Server & OS X Software Update Service roles.