There are already a number of good blog articles on how to get Polycom provision server up and running to provision lots Polycom SIP phones. I would recommend Jeff Schertz blog article .
However as I found, most focus on setting up a Polycom SIP phone using a standard Lync user (with a full AD account and password) and not a common area phone, which has just a AD contact object. Although you could just use an AD user account instead in some environment it is just easier just not have to justify why these accounts have non-expiring passwords.
With the UCS 5.0.2 software it added support Lync PIN authentication and although with a Polycom VVX phone it is easy enough to manually logon the phone using the screen and keypad. As I found with a Polycom SoundStructure this isn’t so easy since there is no screen or keypad and especially since UCS 5.2.0 and later the phone’s (or VoIP Ccrd) web interface is disabled by default.
Although it is easy enough to re-enable the web interface via some additional lines in the shared.cfg XML file on the provisioning server at which point you can log to VoIP card into Lync as a Common Area Phone (below).
However when you have a large number of Polycom SoundStructure devices to configured or support then this quickly becomes impractical.
After a bit reading and trial and error, here is the syntax for the [MACADDRESS]–Lync.CFG file to
<?xml version="1.0" encoding="utf-8" standalone="yes"?> <!--UCS Device Configuration file for Lync--> <LYNC reg.1.auth.useLoginCredentials="1" reg.1.auth.loginCredentialType="extensionAndPIN" reg.1.address="firstname.lastname@example.org" device.logincred.extension="1234" device.logincred.extension.set="1" device.logincred.pin="5551234" device.logincred.pin.set="1" />
Then you just need to reset the VVX/VoIP card for it just automatically logon.
 Provisioning Polycom SIP Phones