Apr 05, 2019  Skype for Business 2016 for MAC. Skype for Business/Lync for Windows. Log out of Skype for Business/Lync. Delete sipprofileName folder. Delete all files in Tracing folder. Do not delete the folder itself. Clear DNS cache: in Command Prompt run ipconfig / flushdns command. Jan 07, 2016  The cache is to minimize the bandwidth consumption of the Skype for Business (Lync) client, since it retrieves a lot of information from cache. This cached information is stored in the users SIP Profile in a folder named sip(SipURI of the user) located on a Windows computer in the following folder, depending of the client version.

Last year, I had a project that involved migrating a large customer from Office 365 Dedicated to Office 365 GCC (multi-tenant). While Exchange hybrid moves were possible for the mailboxes, we were unable to perform the necessary hybrid migration configuration for Lync to migrate users. While Lync was configured and available, not many end users actively used it.

To that end, we decided to just leave them as-is in the legacy environment and light up new accounts in Office 365. We configured the appropriate Skype DNS entries (like _lyncdiscover, etc) and were off to the races.

It worked fine for people who had never used Lync or Skype before, but users who had previously logged into the old Lync environment kept trying to contact the previous environment, despite no DNS records pointing there. The problem lies in the way Lync and Skype cache logon data.

After the first successful connection to Lync or Skype, a cache file directory is created at %userprofile%AppDataLocalMicrosoftOfficex.xxLyncsip_<sipusername>. You’ll find the file endpointconfiguration.cache which has a whole bunch of stuff. If you’re curious to see a little bit of what it has:

It’s not perfect by any means, but you should be able to decipher the URLs that are saved as part of the cache configuration:

So, regardless of whether or not you clear your sign-in credentials, this is the list of what Skype/Lync will attempt to connect to when launching. The only ways to get Skype/Lync to ignore the cache file are:

1. Block network access to the specified networks (firewall, null route, etc).
2. Remove the Skype cache.

I’m not going to write routing statements or firewall rules for you (in this post–I’ve definitely got some things cooking since I lived a previous life as a Cisco guy), but I will give you a quick and dirty script to wipe out the cache per workstation. You can add it to a computer start-up script to and execute once upon user login (maybe set a reg key in HKLM so you don’t keep re-running it).

Convert OFX to QFX (Web Connect) and import into Quicken 2019, 2018, 2017, 2016 (Win/Mac) Step by step instructions for Windows. See below steps for the Windows version. Import created QFX file into Quicken. Now the QFX file is created. Step by step instructions for macOS. Make sure you are. When using file/import, Quicken does list.OFX as a valid format for import. The icon for the.OFX file on the Mac shows the Quicken logo, and right clicking shows Quicken app under 'open with'. Thank you for clarifying that! Have you tried importing the OFX file? If so, what does it say or what happens? If this doesn't work and the bank doesn't provide a QFX file of these transactions, then the transactions can't be imported into Quicken. Import created QIF file into Banktivity. Now the QIF file is created, let's switch to Banktivity and import created QIF file. Before importing a QIF file make sure to backup your data. To import a QIF file, select 'File' - 'Import transactions'. Then click 'Import File' and select created QIF file. Select a Quicken account to import. Import to quicken.

Of course, since this is a script that deletes things, it goes without saying to test this in your own environment.

You can get deleting to your heart’s content here: https://gallery.technet.microsoft.com/Delete-Skype-and-Lync-9d8cf887