Hi Steve, We have actually had tons of headaches which are not yet resolved... but need to be soon, since we had planned a roll-out for April/May. I will keep you posted. That said, I think you still have access to the IT help which is formerly RC and their staff seem to be so much more helpful than the general HUIT people we have assigned to our department. Sincerely, Sylvia, _____________________________ Sylvia Welsh, MS LIS, CSI, LEED AP BD+C Harvard Property Information Resource Center 1350 Massachusetts Avenue, 547 Cambridge, MA 02138 T 617-496-8275 F 617-495-0559 From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Rothman, Steve Sent: Thursday, March 29, 2018 2:29 PM To: [log in to unmask] Subject: Re: Running TMS servers on Amazon cloud AWS ? That's very interesting!!! If you expect to be in production in a month or two, that must mean you already have a semi-working cloud setup going now? If so that's great, congratulations! and in any event I'm very curious about how this goes. Can you fill us in a bit about your current inhouse system and what sort of cloud resources you'll be using to replace it? Any thoughts about performance issues? -Steve Steve Rothman, Systems Administrator Peabody Museum of Archaeology and Ethnology - mobile: 617-517-4855 or x5-9968 From: The Museum System (TMS) Users <[log in to unmask]<mailto:[log in to unmask]>> On Behalf Of Vang-Cohen, Yer Sent: Thursday, March 29, 2018 1:46 PM To: [log in to unmask]<mailto:[log in to unmask]> Subject: Re: Running TMS servers on Amazon cloud AWS ? Hi Steve, We're currently migrating to Microsoft Azure and won't be in production till end of April or May. I'd be happy to answer any questions you might have. Best, Yer Yer Vang-Cohen Data and Database Administrator Information Technology Yale University Art Gallery T: 203-436-9563 | [log in to unmask]<mailto:[log in to unmask]> http://artgallery.yale.edu/<https://urldefense.proofpoint.com/v2/url?u=http-3A__artgallery.yale.edu_&d=DwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=IAfgDO50mhzcsFpE0REakon-Kb_GZrfC2xjwxfmNTQY&m=xhQjDc1ygauVOvwQa5GtEDb4uyVyq6Qmi1Kii5hBCtM&s=mMEl_A2wlBP0V7jrGKOoBkiNnV8lOX-_hIrJGD3mjBA&e=> Now on View Japan's Global Baroque, 1550-1650 February 23, 2018-May 21, 2018 Joel Shapiro: Plaster, Paper, Wood, and Wire March 2, 2018-June 10, 2018 Manuel Neri: The Human Figure in Plaster and on Paper March 2, 2018-July 8, 2018 Pompeii: Photographs and Fragments Through Sunday, August 19, 2018 Sol LeWitt Wall Drawings: Expanding a Legacy Through Sunday, July 8, 2018 From: The Museum System (TMS) Users <[log in to unmask]<mailto:[log in to unmask]>> On Behalf Of Rothman, Steve Sent: Thursday, March 29, 2018 1:23 PM To: [log in to unmask]<mailto:[log in to unmask]> Subject: Running TMS servers on Amazon cloud AWS ? I posted a message about three years ago, asking if anyone had tried running TMS servers using Amazon AWS cloud resources. There were a few responses, but not many. But it's 3 years later now, and I believe Gallery System's own hosted TMS product is running on AWS. Has anyone out there set up their own TMS servers in the cloud, AWS or elsewhere? -Steve Steve Rothman, Systems Administrator Peabody Museum of Archaeology and Ethnology mobile: 617-517-4855 or x5-9968 [log in to unmask]<mailto:[log in to unmask]> To unsubscribe, send an email to [log in to unmask]<mailto:[log in to unmask]> with the following commands in the body of the email: signoff TMSUSERS // eoj You will receive a confirmation that your subscription has been removed. To unsubscribe, send an email to [log in to unmask]<mailto:[log in to unmask]> with the following commands in the body of the email: signoff TMSUSERS // eoj You will receive a confirmation that your subscription has been removed. To unsubscribe, send an email to [log in to unmask]<mailto:[log in to unmask]> with the following commands in the body of the email: signoff TMSUSERS // eoj You will receive a confirmation that your subscription has been removed. To unsubscribe, send an email to [log in to unmask] with the following commands in the body of the email: signoff TMSUSERS // eoj You will receive a confirmation that your subscription has been removed.