Forum Thread

Outlook 2013 - Out of Office Rules can't be saved

LiquidRetro 12,661 4,824 June 12, 2014 at 02:18 PM
I have had several Outlook 2013 users who have been unable to make changes to the rules they have setup (Or save new ones) for out of office. It says it can't save the changes. Outlook is up to date with patches. The server is an Exchange 2008 machine with current service packs and rollups. Server was last rebooted about a month ago. Planning a reboot this weekend for windows updates.

Any one else seen this? Or have ideas to get it running again?

9 Comments

1

Sign up for a Slickdeals account to remove this ad.

Joined Jun 2005
Let Sleeping Dogs Lie
5,842 Posts
2,384 Reputation
Pro
#2
have they tried the web access?
Reply Helpful Comment? 0 0
Joined Aug 2007
L10: Grand Master
6,143 Posts
2,278 Reputation
#3
You can restrict those rules on the Exchange server - are you sure they're set to allow out-of-office messages?
Reply Helpful Comment? 0 0
Joined Aug 2005
L10: Grand Master
12,661 Posts
4,824 Reputation
Original Poster
Pro
#4
Quote from komondor View Post :
have they tried the web access?
In OWA the only thing I see how to do is turn out of office on or off. I don't see a place to edit the rules to say forward to another employee.

Quote from Jeffbx View Post :
You can restrict those rules on the Exchange server - are you sure they're set to allow out-of-office messages?
They didn't use to be. I can still turn Out of Office on, I just can't change the rules that would allow me to forward email to another employee. Do you know where this rule is? I don't know exchange that well.
Reply Helpful Comment? 0 0
Vague questions receive vague answers . . . . . .
Joined Jun 2005
Let Sleeping Dogs Lie
5,842 Posts
2,384 Reputation
Pro
#5
In OWA it is under actions should be on the right
Reply Helpful Comment? 0 0
Joined Aug 2005
L10: Grand Master
12,661 Posts
4,824 Reputation
Original Poster
Pro
#6
Quote from komondor View Post :
In OWA it is under actions should be on the right
Ya I have that, however I was not clear. The rule only applies when Out of Office is Turned on. I don't see that in OWA.

This is what I am talking out in Outlook 2013.
Reply Helpful Comment? 0 0
Joined Aug 2007
L10: Grand Master
6,143 Posts
2,278 Reputation
#7
Quote from LiquidRetro View Post :
They didn't use to be. I can still turn Out of Office on, I just can't change the rules that would allow me to forward email to another employee. Do you know where this rule is? I don't know exchange that well.
Give this article a try: http://blogs.technet.com/b/exchan...95024.aspx
Reply Helpful Comment? 0 0
#8
I don't have a lot of experience with this, either, But -- are your users setting rules on a company computer that accesses Exchange from within the company, or are they accessing with mobile devices such as laptops or cell phones thru OWA from outside the company domain?

On another note, it is my experience working in an Enterprise environment that Windows updates and patches, as well as Office updates and patches are deployed weekly. It doesn't matter if you patch auto from Microsoft or if you use an update process thru WSUS or an installed program\paid for service that manages patches for you such as Netcomply -- the patches are still deployed weekly. Check your schedules for updates/patches and reboot your Exchange on a weekly basis. This will help alleviate a lot of issues. If your patches are loading weekly but you are repressing the reboot until it is 'convenient' to do a reboot, your patches are still not loaded and working until you actually reboot the machine. Having patches in a pending state causes conflicts not only with servers, but also with workstations (desktops and laptops) that a simple reboot can fix right quick. A month time between reboots is too long. We deploy patches on Wednesday evening and reboot all servers at 6am Thursday morning. We ask all our users on workstations to reboot sometime during the day on Thursday, as well.

When we need to forward messages for a user to another user, we are using office 2010, and I believe we are using Exchange 2007 on our server. So the procedure might be a lot different for 2013 -- but the jist of it is that a domain admin has to go into Exchange and set that forward on the server itself -- users can only set out of office messages, they cannot forward their email to another user themselves. We get a notice that it needs to be done for whatever dates a user is on vacation and we set it, then we undo the setting when the user returns from vacation. Enterprise environment that utilizes Active Directory.
Reply Helpful Comment? 0 0
Last edited by callpocket June 13, 2014 at 07:54 PM
R.I.P Tyson the avatar dog December 16, 2013. nod

Sign up for a Slickdeals account to remove this ad.

Joined Aug 2005
L10: Grand Master
12,661 Posts
4,824 Reputation
Original Poster
Pro
#9
Quote from callpocket View Post :
I don't have a lot of experience with this, either, But -- are your users setting rules on a company computer that accesses Exchange from within the company, or are they accessing with mobile devices such as laptops or cell phones thru OWA from outside the company domain?

On another note, it is my experience working in an Enterprise environment that Windows updates and patches, as well as Office updates and patches are deployed weekly. It doesn't matter if you patch auto from Microsoft or if you use an update process thru WSUS or an installed program\paid for service that manages patches for you such as Netcomply -- the patches are still deployed weekly. Check your schedules for updates/patches and reboot your Exchange on a weekly basis. This will help alleviate a lot of issues. If your patches are loading weekly but you are repressing the reboot until it is 'convenient' to do a reboot, your patches are still not loaded and working until you actually reboot the machine. Having patches in a pending state causes conflicts not only with servers, but also with workstations (desktops and laptops) that a simple reboot can fix right quick. A month time between reboots is too long. We deploy patches on Wednesday evening and reboot all servers at 6am Thursday morning. We ask all our users on workstations to reboot sometime during the day on Thursday, as well.

When we need to forward messages for a user to another user, we are using office 2010, and I believe we are using Exchange 2007 on our server. So the procedure might be a lot different for 2013 -- but the jist of it is that a domain admin has to go into Exchange and set that forward on the server itself -- users can only set out of office messages, they cannot forward their email to another user themselves. We get a notice that it needs to be done for whatever dates a user is on vacation and we set it, then we undo the setting when the user returns from vacation. Enterprise environment that utilizes Active Directory.
They are setting rules from their normal workstations within the company.

Windows updates and microsoft updates only come out on monthly. There are from time to time emergency updates the come out in the middle of the cycle but it's rare. Microsoft does this on the Second tuesday of the month to help everyone manage the patches. It would be a nightmare if they didnt. I always install patches and reboot at that time, usually the weekend since people are not using the system.

Ya what your describing for how you do it is what I am doing as a work around. I work in a small company so having users have the ability to forward their own email is nice. I didn't take it away on purpose so I am just not sure why it's doing this all of the sudden.
Reply Helpful Comment? 0 0
#10
Quote from LiquidRetro View Post :
They are setting rules from their normal workstations within the company.

Windows updates and microsoft updates only come out on monthly. There are from time to time emergency updates the come out in the middle of the cycle but it's rare. Microsoft does this on the Second tuesday of the month to help everyone manage the patches. It would be a nightmare if they didnt. I always install patches and reboot at that time, usually the weekend since people are not using the system.

Ya what your describing for how you do it is what I am doing as a work around. I work in a small company so having users have the ability to forward their own email is nice. I didn't take it away on purpose so I am just not sure why it's doing this all of the sudden.
When you use Active Directory and Exchange, I think it must take away some of the settings a user would have available if they were at home -- due to the security associated with the company network. So, as a network Admin, you must set this for your users and take it away when the time span is over.

As far as MS only pushing updates monthly -- well, I don't see that in my network. It may be netframework or office, or some out of the way recommended update, or even Internet Explorer (which we are locked into here at work), but we seem to get something each week. Maybe due to the exploits that have been numerous in the last year, or even from Netcomply testing for 2 weeks before we actually have the updates available to deploy.

Even at home, I still get notices that new updates are available pretty regularly on Wednesday -- and I do see the notices and take action on them at home because I don't let updates load auto at home. I like to see what the update is and what it's for before I load it.

On the company network, we also have schedules to update some other stuff -- like Adobe programs and Malwarebytes (program) and security definitions, as well as Java updates. So a reboot after those updates is pretty important. Malwarebytes is a secondary program that works in conjunction with our AV. AV updates come out periodically during the week, and a weekly reboot is needed for those updates -- so you can see that all of it works together and all can be synced to a scheduled reboot once a week.

If you are not updating Adobe and Java weekly, well, there is some risk associated with that because both of these programs have had a ton of exploits week after week in the last year. If you are disregarding the need to reboot for AV auto updates and waiting a month for that, well, there is more risk associated with that. No, not all AV updates require a reboot, but why take the chance on seeing an alert that this week it doesn't need it and next week it might? Do you have anything other than a pop up on a user computer that tells you it's time to reboot to load an AV update? What AV are you using?
Reply Helpful Comment? 0 0
Last edited by callpocket June 17, 2014 at 08:42 PM
Page 1 of 1
1
Join the Conversation
Add a Comment
 
Copyright 1999 - 2016. Slickdeals, LLC. All Rights Reserved. Copyright / Infringement Policy  •  Privacy Policy  •  Terms of Service  •  Acceptable Use Policy (Rules)  •  Interest-Based Ads
Link Copied to Clipboard