Uncategorized

Office365: setting maximum mail transport limits (email+attachments)…

https://community.spiceworks.com/how_to/65562-office365-setting-maximum-mail-transport-limits-email-attachments

 

Office365: setting maximum mail transport limits (email+attachments)…

Introduction

** NOTE ** The parameters -“InternalDsnMaxMessageAttachSize” and “ExternalDsnMaxMessageAttachSize” are no longer recognized by the Azure PS add-on module; even though the parameters are visible upon viewing a “Get-TransportConfig”. Apparently Microsoft has now set all attach sizes to/from Office365 mailboxes (somehow I doubt this) to 25MB. The article supplied by MS on this is:

https://technet.microsoft.com/en-us/library/exchange-online-limits.aspx#TransportRuleLimits
** END NOTE **

Hopefully this helps someone else out there; the amount of PowerShell commands and cmdlets can be quite overwhelming, and knowing what add-on you need for PowerShell to manage your Office365 installations can be a big time waster.

Here are my notes.

Steps (11 total)

1

What version of PS do you have?

Windows 7 comes with PowerShell v2 as part of the package, and Win8 comes with v3. If you’re using Vista or XP you’ll have to update to at least v2; but that’s outside of this post.

2

Install Microsoft Online Services Sign-On Assistant for IT Pros:

3

Install Windows Azure AD Module (may be unnecessary for this procedure, but will be necessary for others – I install it by default)

4

Reboot after install.

Yeah, you know where that is – the power switch. Or the Start menu/shutdown/reboot. If you’re feeling plucky, Win+R “shutdown /r” – of course there will be some scripting people commenting later on other ways too 🙂

5

Start PowerShell

Start PowerShell as admin (you will notice a new program group-Windows Azure Active Directory with a PowerShell shortcut; it’s safe to start this or the main PowerShell program for our purpose).

6

The COMMANDS – feel Powerful yet?

Once in PS, and **having your admin credentials for your Office365 subscription**, enter the following commands;

$LiveCred = Get-Credential

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential $LiveCred -Authentication Basic –AllowRedirection

Import-PSSession $Session

7

Let’s see what our values are here…

Get-TransportConfig

8

Explanation to Get-TransportConfig

‘ Now – pay special note to the output from this last command, “Get-TransportConfig” – look for the lines “InternalDsnMaxMessageAttachSize” and “ExternalDsnMaxMessageAttachSize”. This is your current max for outbound and inbound emails. Most likely it’s at 10MB, and not what you want.

9

Set the new maxmessagesize…

Set-TransportConfig -InternalDsnMaxMessageAttachSize (nn)MB

‘ Change the (nn) to a number – in meagabytes – that you want for your maximum. Might be 20, 40, etc… supposedly the global max is 25.

‘ example:

Set-TransportConfig -InternalDsnMaxMessageAttachSize 20MB

10

Set the external maxmessagesize…

Set-TransportConfig -ExternalDsnMaxMessageAttachSize (nn)MB

‘ Again, see above note on what to replace (nn) with…
‘ Example:

Set-TransportConfig -ExternalDsnMaxMessageAttachSize 20MB

‘ This will set the max incoming message size (individually) to 20MB – as I understand it.

11

Now check your settings and kick back…

Get-TransportConfig

‘ Now check your config the “*maxmessageattachsize” variables- you should see your new max sizes replaced with what you programmed.

Conclusion

‘ Good luck!

Advertisements

SQL Server 2008, can’t save changes to tables

 

https://chrisbarba.com/2009/04/15/sql-server-2008-cant-save-changes-to-tables/

SQL Server 2008, can’t save changes to tables

When you design a table in a database and then try to make a change to a table structure that requires the table to be recreated, the management tools will not allow you to save the changes.
You will get an error stating, “You have either made changes to a table that can’t be re-created or enabled the option Prevent saving changes that require the table be re-created.”

What a pesky problem.  It prevents you from making progress when you making database changes. It’s a good thing you can turn it off.
This is caused when you make one of the following changes:

  • You change the Allow Nulls setting for a column.
  • You reorder columns in the table.
  • You change the column data type.
  • You add a new column.

Here’s how you fix it.
In Management Studio, go to Tools –> Options –> Designers –> Tables and Designers and uncheck the Prevent Saving Changes that require table re-creation option.
image

Now Management studio will work like expected.

 

WARNING:
Microsoft recommends you don’t turn this option off and that you use T-SQL to make changes to your tables.
Turning off this option will conflict if you have Change Tracking feature turned on.  If you turn off this option and make a change to table with change tracking on all the tracking changes  for that table will also be deleted.
To check if you have change tracking turned on, right click on your table and go to properties, look for the option Change Tracking.

image

Here is the kb article from microsoft: http://support.microsoft.com/default.aspx/kb/956176

 

[SOLVED] You do not have permission to view this object’s security properties, even as an administrative user

http://answers.microsoft.com/en-us/windows/forum/windows_8-security/you-do-not-have-permission-to-view-this-objects/5939dbf4-ca81-4f14-b455-ede115af924e

I spent significant amount of time trying to resolve this and finally succeed.

This is what you gotta do:

Right click/properties/security/advanced/change permissions/add/advanced/find now./

NOW THE MOST IMPORTANT PART:

(I suggest changing the search location to the local server)

Find the line that states ‘Authenticated users’ Click on that ,OK,ALLOW FULL ACCESS.

It might prompt you to confirm or to restart windows or the file.

 

Windows 10 Managing Hyper-V Can’t Connect

https://social.technet.microsoft.com/Forums/en-US/1cc9115d-5fce-4a64-a90f-d3fdc008b861/windows-10-build-10240-managing-hyperv-on-2012-r2-datacenter-cannot-connect?forum=winserverhyperv

696069

 

If the error message is “The WS-Management service cannot process the request.  The class Msvm_RegisteredProfile does not exist in the root/interop namespace” it’s a bug in an HP specific update.  Recompiling the .mof should fix it.

run “MOFCOMP %SYSTEMROOT%\System32\WindowsVirtualization.V2.mof”

If receiving “can’t connect” errors for other reasons, it could be because remote management isn’t enabled or alternate creds or an IP is being used to connect to a down-level host.

 

[SOLVED] Windows Update remains at “Checking For Updates” forever…

http://answers.microsoft.com/en-us/windows/forum/windows_7-update/following-a-clean-install-windows-update-remains/ff3c442e-79a6-40d3-ac35-29e130cebef1

 

1) Download KB3083710 and KB3102810 in advance.

2) Disconnect the computer from the Internet so Windows Update cannot automatically update itself to 7.6.7600.320.

3) Perform a fresh reload from Recovery Media or Windows 7/64 with SP1 RTM.

4) Manually install KB3083710 and restart – WU components will now be version 7.6.7601.19016 dated 9/25/2015.

5) Manually install KB3102810 and restart – WU components will now be version 7.6.7601.19046 dated 10/20/2015.

6) Restore the Internet connection and launch Windows Update as normal.

7) After a few minutes, you should have plenty of updates to download and install.

SCCM Clients not installing Updates

WUAHandler.log Error

OnSearchComplete – Failed to end search job – 0x80244007

Scan failed with error = 0x80244007

 

Uninstall KB3159706 or –

 

https://social.technet.microsoft.com/Forums/exchange/en-US/59ad21be-7514-46df-adf3-fdf6ec15e132/wsus-breaks-after-kb3159706-released-552016?forum=winserverwsus

Hey all, just installed KB3159706 on my WS 2012 R2 WSUS Server at 2PM on 5/5/2016.  This was supposed to fix/issues when KB3148812 was released a few weeks ago.  Don’t install KB3159706, it breaks WSUS.

C’mon Microsoft, get your stuff together.  I’m tired of this amateur hour BS.

 

Shane – Did you do the manual post installation steps after installing KB3159706?

Manual steps required to complete the installation of this update

  1. Open an elevated Command Prompt window, and then run “C:\Program Files\Update Services\Tools\wsusutil.exe postinstall /servicing” (case sensitive, assume C: as the system volume).
  2. Select HTTP Activation under .NET Framework 4.5 Features in the Server Manager Add Roles and Features wizard.
  3. Restart the WSUS service.