[cisco-voip] Bulk updating CIPC (IP Communicator) TFTP Servers

[Brian Meade]

Tommy,

That's a good idea.  I'll look into the feasibility.


On Fri, Aug 3, 2018 at 8:32 AM Schlotterer, Tommy <tschlotterer at presidio.com>
wrote:

> Can you push out a scheduled task that will execute the registry file and
> run as administrator on the night of the cutover?
>
>
>
> Push the scheduled task several days/weeks before the cutover to confirm
> all the PC’s have the scheduled task set. You could also include a script
> to have the PC append a text file with the computer name so you have an
> exact list of all the PC’s that have the scheduled task.
>
>
>
> Thanks
>
> Tommy
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] *On Behalf
> Of *Brian Meade
> *Sent:* Thursday, August 2, 2018 4:43 PM
> *To:* Eric.Isakson at ogdenclinic.com
> *Cc:* cisco-voip voyp list <cisco-voip at puck.nether.net>
> *Subject:* Re: [cisco-voip] Bulk updating CIPC (IP Communicator) TFTP
> Servers
>
>
>
> *EXTERNAL EMAIL*
>
>
>
>
>
> Looks like the issue there is it could take up to a day according to some
> Windows guys I talked to.  Have you seen quicker pushes through GPO?
> Looking at ~1,000 PCs and the idea is their IP Communicator would just be
> good to go when they logon the next morning even if on VPN.
>
>
>
> On Wed, Aug 1, 2018 at 6:48 PM Eric Isakson <Eric.Isakson at ogdenclinic.com>
> wrote:
>
> If on a Windows domain with domain-joined workstations, Group Policy
> Preferences should work well here.  Target the computer (as opposed to the
> user) and you should be able to update HKLM.
>
>
>
> /Eric
>
>
>
>
>
> *From:* cisco-voip <cisco-voip-bounces at puck.nether.net> *On Behalf Of *Brian
> Meade
> *Sent:* Wednesday, August 1, 2018 7:48 AM
> *To:* cisco-voip voyp list <cisco-voip at puck.nether.net>
> *Subject:* [cisco-voip] Bulk updating CIPC (IP Communicator) TFTP Servers
>
>
>
> Hey everyone,
>
>
>
> I'm working on a project now migrating from one cluster to another.  Bulk
> updating the TFTP Server entries for CIPC has proven to be more difficult
> than originally assumed.
>
>
>
> Through a lot of trial and error, I found this is the correct registry
> location for 64-bit machines:
>
> HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Cisco Systems, Inc.\Communicator\
>
>
>
> There's also an entry in HKCU that is overridden by the HKLM entry.
>
>
>
> We're looking at ways to bulk update this registry entry.  SCCM running
> the script doesn't seem ideal as it can take up to an hour after logging
> into the VPN for users to check in and run the SCCM script.
>
>
>
> We've pushed a local registry file to everyone's machines to allow them to
> manually run it but HKLM requires them to elevate their accounts to local
> admin.
>
>
>
> Has anyone found a way to do this fairly seamless to the end users?
>
>
>
> Thanks,
>
> Brian Meade
>
>
> ------------------------------
>
> This information belongs to Ogden Clinic, is confidential, and may be
> legally privileged. It is intended solely for the addressee. Access to this
> information by anyone else, unless expressly approved by the sender or an
> authorized addressee, is unauthorized. If you are not the intended
> recipient, any disclosure, copying, distribution or any action omitted or
> taken in reliance on it, is prohibited and may be unlawful. If you believe
> that you have received this email in error, please contact the sender,
> delete this email, and destroy all copies.
>
>
> Tommy Schlotterer | Systems Engineer - Collaboration
> Presidio (NASDAQ: PSDO) | presidio.com
> 20 N Saint Clair 3rd Floor, Toledo, OH 43604
> D: 419.214.1415 | C: 419.706.0259 | tschlotterer at presidio.com
>
>
>
>
> *This message w/attachments (message) is intended solely for the use of
> the intended recipient(s) and may contain information that is privileged,
> confidential or proprietary. If you are not an intended recipient, please
> notify the sender, and then please delete and destroy all copies and
> attachments. Please be advised that any review or dissemination of, or the
> taking of any action in reliance on, the information contained in or
> attached to this message is prohibited.*
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180803/278fbff8/attachment.html>