![]() ![]() So the data is still there, and the Shoretel import process can still importĪ properly-formatted CSV file. In the process, public folders are no longer, and the data from the one we need now exists as the default contact list for a particular shared mailbox. csv file into the Shoretel directory.Īnd then we moved to Office 365. csv file, then the batch file called a Shoretel process that imported the contents of that. Once the Shoretel EXE used those parameters to extract the data and create the. 1 OurExchangeAdminName OurAdminPassword 1000 Operations ImUri,ContactDetails ImportPublicContacts.log ImportPublicContacts.csv The XML configurationįile for that process should give some clue how they were using ExchangeWS, and a couple of Exchange DLLs sat in the same folder. The batch file simple passed arguments to a Shoretel EXE that presumably called ExchangeWS API to extract data from the public contacts folder and create a. ![]() This all ran as a scheduled task that called a batch file. ![]() Instead, all the numbers are simple available in our Shoretel directory. To propagate all those contacts into their personal Outlook contacts and using MAPI to synch with Shoretel. We originally had on-premises Exchange 2010 and had a tool to pull the contents of a particular public contacts folder into our Shoretel directory so that all our company drivers' numbers were accessible for dialing within Shoretel without requiring each user csv file containing data from the contact list in an Office 365 shared mailbox. I need to automate the process of pulling a. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |