Junk Mail Filtering in Outlook - it will be gone

On No1/11/20166,  1/11/2016, Microsoft will stop releasing updates to Junk Email definitions for Outlook's junk Email filter. The junk email filter will continue to work in Outlook, using the last definition installed, it just won't be updated going forward, which will reduce its effectiveness in the future. The SmartScreen filter in Exchange Server is also affected and will not be updated going forward.

SmartScreen Spam filtering was introduced in Outlook 2003, moving suspected spam (and occasionally, valid messages) into the Junk Email folder. It's not perfect by any means as client-side filtering has a couple of problems: if you use multiple computers, each Outlook w

Palo Alto Network single pass Platform architecture

Date plane

Control plane

windows 10 join windows 2003 domain and windows 2003 domain upgrade to windows 2016 domain

windows 10 join windows 2003 domain and windows 2003 domain upgrade to windows 2016 domain

it is all supported

https://technet.microsoft.com/en-us/windows-server-docs/identity/ad-ds/windows-server-2016-functional-levels

(quote)

With the end of life of Windows 2003, Windows 2003 domain controllers need to be updated to Windows Server 2008, 2012 or 2016. As a result, any domain controller that runs Windows Server 2003 should be removed from the domain. The domain and forest functional level should be raised to at least Windows Server 2008 to prevent a domain controller that runs an earlier version of Windows Server from being added to the environment.

We recommend that customers update their domain functional level (DFL) and forest functional level (FFL) as part of this, since the 2003 DFL and FFL have been deprecated in Windows Server 2016 and they will no longer be supported in future releases.

For customers who need additional time to evaluate moving their DFL & FFL from 2003, the 2003 DFL and FFL will continue to be supported with Windows 10 and Windows Server 2016 provided all domain controllers in the domain and forest are either on Windows Server 2008, 2012 or 2016."

At the Windows Server 2008 and higher domain functional levels, Distributed File Service (DFS) Replication is used to replicate SYSVOL folder contents between domain controllers. If you create a new domain at the Windows Server 2008 domain functional level or higher, DFS Replication is automatically used to replicate SYSVOL. If you created the domain at a lower functional level, you will need to migrate from using FRS to DFS replication for SYSVOL. For migration steps, you can either follow the procedures on TechNet or you can refer to the streamlined set of steps on the Storage Team File Cabinet blog.

The Windows Server 2003 domain and forest functional levels continue to be supported, but organizations should raise the functional level to Windows Server 2008 (or higher if possible) to ensure SYSVOL replication compatibility and support in the future. In addition, there are many other benefits and features available at the higher functional levels higher. See the following resources for more information: 

migrate SBS server to server 2012 / 2012 R2

migrate SBS server to server 2012 / 2012 R2

https://blogs.technet.microsoft.com/infratalks/2012/09/06/transition-from-small-business-server-to-standard-windows-server/

https://social.technet.microsoft.com/Forums/en-US/59f66dcf-f74f-4b4c-aa84-c631724b3d13/sbs2011-to-2012-r2-migration-wo-exchange?forum=winserverMigration

(quoted here)

• For SBS 2011 to 2012 R2 migration without Exchange, brief steps here:
  1. Install Server 2012 on the new server, join to the domain. ( Upgrade the schema etc... on the old server with 2012 DVD)
  2. Promote it to a domain controller, make it a global catalog server and a DNS Server.
  3. Wait for everything to replicate, then move your data if needed.
  4. Install DHCP on the new server (same scope as the SBS 2011), then shut down DHCP services on the SBS server and activate on the new server.
  5. Transfer the FSMO roles.
  6. DC Promo the SBS server out of the domain.
  7. Shut down the SBS server.
  Please refer to following articles and threads to get more information:
  These steps are applicable for transition from all the versions of Small Business Server to Windows Server 2008/ 2008 R2/ 2012.

image my notebook hard drive to a replacement hard drive - HP notebook PC Probook 650 G1

image my notebook hard drive to a replacement hard drive - HP notebook PC Probook 650 G1

it turns out as a challenge,

my notebook hard drive OS upgraded from w7 to w10.

to my horror the other week, it failed to create recovery discs. it says there are bad clusters on the hard drive

it still under warranty, so i called HP, actually chatted with HP support. they sent me a replacement hard drive

now I want to copy my current disc to the target disc

I tried reflect.exe -- Macrium - free version could not do as my drive has dynamic volumes

I turned to the paid Stagecraft IT edition, I captured the image, but after I restore the image to the new drive, i got press ctrl+alt+del

the disc wont boot ....

contact StorageCraft support, I am told use the x64 RE, I did, same issue

something like BCD broken, repair failed

I checked the source drive structure again, there are heaps of partitions ,

I NOTICED there is 1 partition NTFS - 1GB -- no drive letter -- pri, active, in addition to C: D: I did previously

I imaged this over, BCD error disappeared on C:

then my w10 boots up

but I dont have to do this for w7. I have to do this system partition for w10 on my notebook

took a long