Outlook 2010 – File Attachment Limit
“The attachment size exceeds the allowable limit"
[HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Preferences]
and adding a new DWORD value:
MaximumAttachmentSize
and setting its value to 0
“The attachment size exceeds the allowable limit"
[HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Preferences]
and adding a new DWORD value:
MaximumAttachmentSize
and setting its value to 0
How could something like CRUD be desirable? In Group Policy world, even the impossible becomes possible. In this entry, you’ll discover why Red does not mean Error and what the different colors mean when you make a Preference item. Read on!
Let’s talk about some of the intricacies of Preferences, specifically what we fondly refer to as CRUD options. Now, keep in mind, CRUD only applies to “stuff”, meaning things you can create and delete on the client, like mapped drives and shortcuts and printers. There are no CRUD options for things you just make changes to but don’t create, like “folder options”. More on this at the end.
Despite it’s unfortunate acronym, CRUD is very useful. It is also the reason those little spots of color get associated with you new Preference items. Select one of the four actions from the drop down menu to choose between Create, Replace, Update, and Delete. That decides how your Preference item will be pushed onto the client. Let’s take drive mappings as an example.
This is the Preference item
(in UI) (in XML)
Now, under the “Action” drop down, you have four options : Create, Replace, Update, Delete
Create – If a drive mapping doesn’t exist for this user for the share “\\share\userDocuments\”, then create one. If there already is one, don’t do anything! It’s a kind, gentle sort of policy, it won’t overwrite anything you already have, so it has a Green icon associated in the UI.
Replace – Remove whatever drive mapping exists for this share, and create a new one with these settings. If there isn’t one, just create it. No matter what, you’re getting this drive mapping, whether something existed there or not. It’s very insistent, like the bully of the CRUD options, so it gets a Red icon.
Update – Yellow – If that drive mapping exists, it will be updated with the settings specified here. If there are other settings associated with the drive mapping that aren’t specified here, they will be maintained. If no drive mapping exists for this share, create it. Nothing gets blasted away like with the Replace setting, but there is still a chance that you’ll overwrite something, so it gets a Yellow icon (warning! make sure you know what you’re going to be over-writing!).
Delete – X mark – If that drive mapping exists, it will be removed. That’s it, it’s just removed, so it gets an ‘x’ icon. It does not roll back, it gets deleted.
What did we learn? Red does not mean error! X marks the (delete) spot. Another picky note is that if you choose the “remove when no longer applicable” option under the common tab, it’ll force the CRUD action to Replace.
So, really, I’d recommend reading the help associated with each Preference item to make sure you know what you’re doing.
Hope that helps!
liliaG aka @superlilia
P.S. The end! Here’s more on my stuff vs. state discussion. Stuff means something that can be created or deleted on the client machine / user account. Think of at is as something you can see appear. It has a new icon that becomes associated with it: when you add a new printer, an icon appears that looks like that printer in your Devices window. When you add a shortcut to the desktop, that shortcut appears. Similarly, when you remove a local security group, it is gone, the icon is removed, the group no longer exists. That doesn’t mean that not all local security groups are gone, just that instance of one.
State is a state of being, like folder options. You can’t “create” a folder options, but you can make changes like “Show all hidden files”.
GP Preferences has both of these types of things, but CRUD only applies to the stuff bits. You can’t configure CRUD for state, and the UI isn’t there to let you try.
P.P.S. Here’s the help in the product:
DFU means Device Firmware Update. If a restore using Recovery Mode doesn’t work you will want to use DFU Mode as a last resort. When placing your iPhone into DFU Mode it does not load the OS before attempting the restore
To put the iPhone into DFU mode so you can do an iTunes firmware restore follow these steps:
Step One
Open iTunes and connect the iPhone to your Mac.
Step Two
Press and hold the Home button and the Sleep/Wake button at the same time.
Step Three
After exactly 10 seconds release the Sleep/Wake button. Continue holding the home button until you iTunes pops up a message telling you that it has detected an iPhone in recovery mode.
The iPhone screen will remain black like this:
NOTE***: It may take a few attempts to get your iPhone into DFU mode. Generally, I hold down both buttons then release the Home button just before I think the Apple logo would appear. If you are still holding both buttons down and you see the Apple logo you are holding them down for too long!
[Today’s post comes to us courtesy of the SBS SE Team]
This article lists the known issues and their workarounds after installing IE 8 on your Small Business Server and the on your Vista clients. This article is for test purposes only. Installing beta products in a production environment is not recommended or supported by PSS.
There will be some known issues after you install IE 8 on Small Business Server 2008 or your Vista clients:
To work around this issue, use one of the following methods.
Method 1: Enable Negotiate (Kerberos) option for Sharepoint 3.0
Follow these steps:
Method 2: This issue will be fixed in upcoming update rollup for SBS 2008; you can download and install it from Microsoft Update when it is available.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\SensLogn]
"DLLName"="WlNotify.dll"
"Lock"="SensLockEvent"
"Logon"="SensLogonEvent"
"Logoff"="SensLogoffEvent"
"Safe"=dword:00000001
"MaxWait"=dword:00000258
"StartScreenSaver"="SensStartScreenSaverEvent"
"StopScreenSaver"="SensStopScreenSaverEvent"
"Startup"="SensStartupEvent"
"Shutdown"="SensShutdownEvent"
"StartShell"="SensStartShellEvent"
"PostShell"="SensPostShellEvent"
"Disconnect"="SensDisconnectEvent"
"Reconnect"="SensReconnectEvent"
"Unlock"="SensUnlockEvent"
"Impersonate"=dword:00000001
"Asynchronous"=dword:00000001