I do the same thing. Typically on Sunday, since we don’t work that day, yet.
Miguel A. Santillan
Compass Manufacturing Systems
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Wednesday, July 15, 2015 8:19 AM
To: vantage@yahoogroups.com
Subject: [Vantage] RE: Epicor and Windows Updates
Even though we have never run into an issue with Windows updates and Epicor. We don’t have them applied automatically. We will do manual scheduled downloads and install after hours about once a month, and then install them, then reboot the servers.
Sigfredo.
From:
vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Wednesday, July 15, 2015 11:04 AM
To: vantage@yahoogroups.com
Subject: [Vantage] RE: Epicor and Windows Updates
We have had issues, but we also have custom applications that interact between Epicor / ADP and our production floor. Last week the updates crashed one of our servers. We try to apply them ourselves, not automatic to keep the impact down, but obviously can still miss.
Brenda
From:
vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Wednesday, July 15, 2015 10:00 AM
To: vantage@yahoogroups.com
Subject: [Vantage] RE: Epicor and Windows Updates
If it’s not broke don’t fix it, run updates quarterly or semiannually.
From:
vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Wednesday, July 15, 2015 08:54
To: vantage@yahoogroups.com
Subject: [Vantage] Epicor and Windows Updates
Hi All,
I was wondering what the consensus is when it comes to keeping Windows Server up to date on your ERP server (9 or 10).
Do you take the approach of always keep Windows Server updated? If yes, have you ever run into an update that created a problem with Epicor?
Do you take the approach of, if it’s not broke don’t fix it, and don’t apply updates?
Or do you take a different approach? For example, review each update and only apply certain ones.
[cid:1b0f60.png@342dd748.4cb721a1]
Joe Rojas
Director of Information Technology
(781) 408-9278 Mobile
(781) 573-0291 Local
(781) 232-5191 Fax
[http://matsinc.com/images/e-mail-signatures/tagline.jpg]
[http://matsinc.com/images/e-mail-signatures/graphics/logo_matsinc.png]<http://matsinc.com> [http://matsinc.com/images/e-mail-signatures/graphics/icon_twitter.png] <http://twitter.com/Mats_Inc>
[http://matsinc.com/images/e-mail-signatures/graphics/icon_facebook.png] <http://www.facebook.com/commercial.flooring> [http://matsinc.com/images/e-mail-signatures/graphics/icon_youtube.png] <http://www.youtube.com/user/MatsIncTV>
[http://matsinc.com/images/e-mail-signatures/graphics/icon_pinterest.png] <http://www.pinterest.com/contractfloors/> [http://matsinc.com/images/e-mail-signatures/graphics/icon_blog.png] <http://matsinc.com/blog>
[Non-text portions of this message have been removed]
This e-mail and any attachments may contain confidential and privileged information. If you are not the intended and/or named recipient or recipients, please notify the sender immediately
by return e-mail, delete this e-mail and destroy any copies. Any dissemination or use of this information by a person other than the intended recipient or recipients is unauthorized and may be illegal. Any views or opinions expressed in this email are those
of the author and do not necessarily represent those of the Specialty Screw Corporation. Warning: Although precautions have been taken to make sure no viruses are present in this email, Specialty Screw Corporation cannot accept responsibility for any loss
or damage that may arise from the use of this email or attachments.
ÂÂ