tag:blogger.com,1999:blog-83053953469353297862011-04-21T22:12:45.947-07:00Chad Gniffkehttp://www.blogger.com/profile/12739173570754454666noreply@blogger.comBlogger11100tag:blogger.com,1999:blog-8305395346935329786.post-41446094501979129352009-02-16T13:49:00.000-08:002009-02-16T13:57:34.912-08:00<p>Joe, </p> <p>This comment was made over Twitter.com a few days ago: Fellow Kaseya admins: The new Exchange patches will probably leave Exchange services offline. Schedule and reboot accordingly.</p> <p>Do you have an insight on this or is there an known issue?</p> <p>Live link: <a href="http://twitter.com/GreyDuck/statuses/1203275693">http://twitter.com/GreyDuck/statuses/1203275693</a></p> <p> <hr width="100%" size="2" />This is not unusual in some patches for both SQL Server and for Exchange Server.&#160; It is strictly dependent on the Microsoft patch. <br />I did pull down these Exchange patches and confirmed the default command line switches.&#160; The default switches are correct.&#160; There are no special switches for these patches.&#160; So, the issue has nothing to do with Kaseya&#8217;s deployment of the patches.&#160; It is something that techs responsible for managing SQL Server and/or Exchange Server should normally be aware of and take into account when patching those servers. <br />Joe</p> <p><a title="network management software" href="http://kaseya.com" target="_blank">network management software</a></p> <div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8305395346935329786-4144609450197912935?l=chadgniffke.blogspot.com' alt='' /></div>Chad Gniffkehttp://www.blogger.com/profile/12739173570754454666noreply@blogger.com0