25 MB mailbox send size for Office 365 online

25 MB mailbox send size for Office 365 online

recover a windows 2008 R2 Xen 5.6 virtual machine --- my Friday rescue series continues -- restore reg file that happened to be backed up

recover a windows 2008 R2 Xen 5.6 virtual machine --- my Friday rescue series continues

well, not this Firday, its last Friday night...

got a call from co-worker and management off-course , that a fileserver ( PDC as well) has reboot and crashed to bluescreen in a cycle.

by looking at the bluescreen code ( I will post the code later here), one possibilty is the drive letter not be assigned in reg. I booted the windows 2008 R2 server into repair mode, not much help.

tried LKG, tried disabled signed-driver, no luck.

another thing is to check runonce... I didn't try this

in despair, I found a copy of reg back files one week ago, and I make a copy of current ones, and copy the backup ones over, namely they are SOFTWARE /, SYSTEM etc

the location is windows\system32\regback

then miracle happened, the server started ...

a few points need noting: 1/ need windows 2008 R2 ISO, luckily , another co-work made it available during the server initial install
2/ local admin password: I guess this out as it is this company's often used one. this is the domain administrator password, i dont think it is the DSRM password. I never tried AD recovery. as the result proved it is reg corrupted.
I need the local admin passowrd to boot the ill-fated VM to repair mode even if it is a PDC.
3/ I performed this remotely via a XEN console , co-work started teamviewer on the XEN console client PC ( W7)

previously I dont think PC system generated reg files are useful as they tend to be old reg when the PC was new.

this time, the system generated reg backup is 1 week old.

upgrading dirsync failed --- eventually remove and re-install

I changed office365 password.

dirsync broken , I run a tool from office.com, I am told dirsync need be upgraded

I tried and tried , nothing worked .... various errors

installing dirsync on a SQL server with a defaul instance, you dont need to specify the password and servername,

eventually logged a case with Microsoft , the support tried, eventually removed the half-installed new version of dirsync, and installed with the same new version.

in the process he said no password prompt will happen, that;s true

Each user can install Office 365 Pro Plus on which of the following?

Each user can install Office 365 Pro Plus on which of the following?

5 Computers, 5 Tablets and 5 Mobile Devices

Q&A Which of the following services is NOT part of Office 365?

Which of the following services is NOT part of Office 365?

Microsoft Intune

windows 10 joined a windows 2003 domain

windows 10 joined a windows 2003 domain

will that still work? mixed results here


https://social.technet.microsoft.com/Forums/en-US/ad819a03-3341-4266-b998-bafbda23b897/windows-10-build-9926-domain-join-on-active-directory-2003-domain-level?forum=WinPreview2014General

Access Denied on USB drives

Access Denied on USB drives

http://h30434.www3.hp.com/t5/Notebook-Operating-Systems-and-Software/Access-Denied-on-USB-drives/td-p/3662944

like a joke

Yes, I done ADFS 3.0 using Windows Azure VM with Office 365 .... here is my version

Yes, I done ADFS 3.0 using Windows Azure VM with Office 365

I thought of doing this for sometime now. eventually with Windows Azure VM, it bit easier to do the test ADFS,

there is a great post I am referring to

http://office365support.ca/setting-up-the-primary-ad-fs-3-0-server-in-windows-azure-for-office365-single-sign-on/

I basically followed the steps listed above ...

here is my implementation ....

0/ a windows azure AD is setup like datasys.biz like DSLPDC

1/ I setup another server like DSLRDS, installed dirsync

2 / verify in azure portal that you own the domain, put ms=xxxx in the dns record. there is a caveat in doing this as I have to create datasys.biz as standalone rather than federated

3/ then convert the datasys.biz to federated domain

4/ plan ADFS structure , in my case, I use Windows Azure only domain, ie no link to on-premise AD. I would say this method will work as hybrid as well.

5/ plan the farm, a ADFS farm with two servers, a webproxy farm with two servers, ADFS servers are domain-joined; web proxies are not domain joined.

6/ in this test, another network created under the azure network as DMZ network...
172.16.16.x as primary   ---- DC, ADFS on this
then 10.118.118.x as DMZ -- 2 webproxy servers on this one

it is routable between this two sub networks

7/ I used internal load-balancing for ADFS,  so I dont need modify the host file approach in the above mentioned link

8/ plan your ADFS name, I would use one name fs.datasys.biz ; this is the name for all adfs-related servers --- 2 ADFS + 2 Webproxy

8.8/ create a service like dataADFS, install VM - ADFS01 inside ( then adfs02)

9/ get a trial cert from comodo (3 month) or geotrust (1 month) ; with the name fs.datasys.biz ; do this on adfs01 ; export the cert with the private key plus password. this will be imported to 3 other servers

10/  install adfs02 , import cert, install adfs role etc

11/ install internal LB with windows azure powershell cmd, the load balancer name is fs.datasys.biz ; this balancer , is not available to internet; you can do internal test by going to
 https://sts.domain.com/adfs/ls/IdpInitiatedSignon.aspx
in my case , its https://fs.datasys.biz/adfs/ls/ldpInitiatedSignon.aspx
this URL is very important for me for testing

12 / now create a WAP service, put datawap01 in it, install the webproxy role under remoteaccess (assuming you use all server 2012 r2) , import cert, then start the configuration wizard ... follow the wizard the federation name is fs.datasys.biz ; I used domain credentails , as local credentials keeps getting error.

13/ install 2nd dawap02, do the same as above, I kept getting error like something like glabal config ; then I viewed the cert, import the cert again, after a long think , ADFS success what a relief.

14/ configure WAP URL load balance, in azure portal, datawap01, enable https end points, create load balance set

15/ for datawap02, add it to the https balance set

16/ note the wap service public IP

17/ in public dns, put the IP to fs.datasys.biz

(note dattasys.biz is an example domain)

18/ test by browsing to portal.office.com

19/ this will re-direct to the fs.datasys.biz

20/ enter a valid username/password in your windows azure VM AD

21/ then it will re-direct you back to portal.office.com as a logged-on user.

22/ yeah, I have finally done ADFS after thinking-of doing this for years

many thank to Kelsey Epps Office365 MVP

outlook 16 connection error to Exchange 2010

outlook 16 connection error to Exchange 2010

there is an error citing EWS,

this happened with my non-domain joined w8.1 ; my w10-domain-joined notebook seemed fine

https://community.office365.com/en-us/office_2016_preview/f/991/t/347764

https://technet.microsoft.com/en-us/library/aa995956(v=exchg.141).aspx

something to do with the autodiscover

office 2016 first impressions --- it looks like replaced my current office 2013 -- O365 subscription

office 2016 first impressions --- it looks like replaced my current office 2013

enable office 2016 preview for download in office 365

enable office 2016 preview for download in office 365

https://support.office.com/en-nz/article/Office-365-release-options-3B3ADFA4-1777-4FF0-B606-FB8732101F47?ui=en-US&rs=en-NZ&ad=NZ

Set up the release option for your organization

You can change how your organization receives Office 365 updates by following these steps.
Important   It can take up to 24 hours for the below changes to take effect in Office 365. If you opt out of First Release after enabling it, your users may lose access to features that haven’t reached the scheduled release yet.

1. Sign in to Office 365 with your work or school account.
2. Go to the Office 365 admin center.
3. Go to Service settings > Updates.
4. To disable first release, select Standard under the Standard release heading.
   To enable first release choose Entire organization or Select people and follow the steps below.

Select people for First Release

Follow these steps to select individual people for First Release. You might, for example, add your IT staff for First Release so they can review features before the rest of your organization. Enable First Release with select people following these steps.

1. Go to the Office 365 admin center.
2. Go to Service settings > Updates.
3. Under first release, choose Select people.
   Note    If you don't see this option in your admin center, your subscription will soon be updated with it and you can change the setting then.
4. Choose Pick people to add users individually and then use the people picker to select them for first release.