When trying to recover from a Windows Image Backup, you may encounter error 0x80042412.
After researching a number of articles mentioning about disk clean, setting active partitions etc, it was found that the majority of people have this issue because of disk type and size.
How to fix
After a bit of time, the simple fix is use the same size disk drive or larger for the recovery.
If using a smaller disk, the original backup partition needs to be same or smaller than the replacement drive.
Microsoft has officially killed off Windows Media Center. Here’s how you can get Windows Media Center running on Windows 10.
Make a quick Windows search for Media Center and it will be your top match, but you can also find it under Window Accessories in the Start menu.
You should be able to run WMC normally from there.
You can also pin to desktop or start menu to make it easier for you.
Posted: Mark Pace
We were banging our head against the wall with the winmail.dat problem we have with an office 365 email account.
The solution is to hack the Office 365 server with regards to the Transport Neutral Encapsulation Format (TNEF) format.
This article describes how Microsoft Office 365 admins can change the message format so that messages that are sent from Office 365 users to external recipients don’t contain the Winmail.dat attachment.
By default, email messages that are sent from Exchange Online in Office 365 use the Transport Neutral Encapsulation Format (TNEF) format. Messaging systems that aren’t based on Microsoft Exchange may be unable to interpret messages that use this rich text format. If the recipient’s messaging system can’t process this format, a file attachment that’s called Winmail.dat is added to the message.
Office 365 admins can use Windows PowerShell to change the message format to prevent the Winmail.dat attachment from being sent to external recipients.
You will need to paste in the following commands:
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell/ -Credential $LiveCred -Authentication Basic –AllowRedirection Import-PSSession $Session Set-RemoteDomain Default -TNEFEnabled $false
The first line asks for your Office 365 (admin account, please!) username and password and connects you to the service.
Line 2 imports the commands you are going to need.
Line 3 prevents TNEF messages being sent outside of your domain.
Setting it to anywhere outside of your domain is a slightly broad brush-stroke, but it does reduce the overhead of having to keep going back and fix it for each domain you discover that cannot cope. But if you really wanted to only disable TNEF for specific domains, you can:
New-RemoteDomain -Name Awkward -DomainName awkward.comSet-RemoteDomain Awkward -TNEFEnabled $false
In the first line you define your awkward domain, in the second you prevent TNEF messages going to it.
Yes, but while it’s a big hammer it’s also nice and sharply targeted…
Set-MailContact <ExternalEmailAddress or GUID> -UseMapiRichTextFormat Never
…will set mail sent to ExternalEmailAddress to always be sent plain text – no formatting at all.
Like stepping back in time.
Some might say a happier time, when people cared about the amount of bandwidth they used, didn’t send huge attachments and didn’t expect everyone to be using Outlook.
Some might say that, not me of course! I’m just thinking it…
(Updated 2014 to change -ConnectionUri from https://ps.outlook.com/powershell/ to https://outlook.office365.com/powershell/)
——————————————————————————————————————————————-
Source with thanks : https://www.deargeek.co.uk/2013/11/how-to-stop-office-365-sending-those-pesky-winmail-dat-attachments
Other sources :https://support.microsoft.com/en-au/kb/2487954
This document is provided by Fortinet Corporation and shown here for customer and staff information only.
Summary
This document is intended to outline the policy that Fortinet has established for the activation date of warranty
and support. Renewals of support contracts will start from the end of the previous support contract.
In Summary
• Product warranty and support starts at the EARLIER of the following events:
−− At time of registration
−− At first point when unit will connect with Fortinet and request updates
−− If these two events do not occur within 100 days of the shipment of product from Fortinet, the
hardware, service and support will be auto-activated 100 days from Fortinet shipment to Distributor
• At initial power-up it is HIGHLY recommended that the customer follow the registration process to ensure
timely updates and support.
Warranty
Warranty/Support start is tied directly to the ship date or activation connection with Fortinet. Warranty is
the base level of coverage on the hardware platform. Fortinet’s warranty is included in its End User License
Agreement.
Support
The start of support is tied to the timing of hardware shipment or activation, but a maximum of 100 days grace
period is provided in EMEA/APAC. Support is considered “insurance” in many ways, meaning it is there in case
something goes wrong, hence it is important that the support agreement starts around the time product is
received and doesn’t wait to start until an issue comes up.
Bundles
The start date for bundles will follow the warranty/support policy above.
Effective Date
This new policy applies to products purchased and shipped from Fortinet on or after October 1st, 2015.
Fortinet is committed to providing regular patches and support services for a period of 36 months from the date of general availability. An additional 18 months beyond this period has been added, bringing the total duration of support for a software or firmware release to 54 months.
This is a way for Fortinet to ensure that we are providing your customers with the most up-to-date Fortinet security protection.
Wondered how you can send a message to all users logged in to a 2012 Server?
Well here it is …
Open a COMMAND PROMPT
Msg * “Buy Me Lunch”
Before you know it, you wont be hungry anymore. 🙂
Have a look at the directory listing from the command prompt using the /a switch which shows all attributes.
