2016
1763 TopicsMicrosoft Office 2019 Now Available – Comparing 2019 vs 2016 vs 365, New Features in Access & Excel
Microsoft Office 2019 is out! Microsoft started the roll-out today of Microsoft Office 2019 for Windows & Mac – with major updates to Access, Excel, Word, PowerPoint, Outlook, Project, Visio, and Publisher – to commercial volume license customers. Microsoft is following up with Office 2019 releases to consumers and other business customers, as well as SharePoint / Exchange / Skype / Project Server 2019 releases, in the coming weeks. Office 2019 provides a subset of features Microsoft has added to Office 365 over the past three years. As Office 2019 is a one-time release, Office 365 is still the better choice with not only far more features (Co-Authoring, etc) unavailable in Office 2019, but also far earlier access to them than on-premises, non-subscription Office 2019, etc. editions. Speculation has been that Office 2019 may be the last perpetual license (on-premises / non-subscription) release of Office, so that Microsoft can focus in on its Office 365 subscription offerings. However, Microsoft has responded in one case that there is likely to be one more perpetual license release after this one. Either way, Microsoft Office 2019 product pages even describe Office 2019 as a "one-time release" with Office 365 being needed to gain access to new features after that. It may also be that there are fewer editions available for Office 2019 than for Office 2016. Whether you move to Office 2019 or 365, it's suggested you don't delay doing so, as Office 2016 cloud support will be dropped in 2020, with Office 2016 installs barred from connecting to Microsoft's cloud-based services, including hosted email (Exchange) and online storage (OneDrive for Business), after Oct. 13, 2020. New in Office 2019 Word – text-to-speech, improved inking & accessibility, focus mode, translator, Learning tools (captions & audio descriptions), @ Mentions PowerPoint – Morph transitions, Zoom, SVG, 3D model, play in-click sequence, 4k video, @ Mentions Excel – Power Query (Get & Transform) enhancements, Power Pivot included with all editions, new functions & connectors, publish to Power BI, AI-driven Excel Insights for chart suggestions, new charts, @ Mentions Excludes Co-Authoring, new Data Types like Stocks, and some other new features only available in Office 365 Outlook – @ Mentions, Office 365 Groups OneNote – OneNote for Windows 10 (Modern App included with Windows) has replaced OneNote desktop app (though OneNote 2016 will be available via Volume License Install tool) All Office apps – Ribbon customizations and roaming pencil case Microsoft Access - including the many updates we've seen recently such as: Modern Charts New Linked Table Manager Dark theme Big Int Salesforce & Dynamics connectors Other Recent Developments with Microsoft Access It's especially exciting to see all the new features, growing user base and communities, new integrations, and development team responsiveness seen with Microsoft Access of late. Inclusion on the Office templates page Which I hope will become permanent soon SQL Server Migration Assistant (SSMA) updates ODBC and OLE DB driver updates – for optimized use and new feature support for SQL Server, Azure SQL and other back-ends databases Power BI support (via On-Premises Data Gateway) Considering On-Premises Data Gateway is shared with PowerApps, hopefully that means we may see PowerApps support too in the future New & growing Access conferences and user communities: New Access Developers' Day in Amsterdam DevCon in Vienna, AEK in Germany, UKAUG in UK, PAUG in Portland, Access Day in Redmond, Access Madrid in Spain Presence at Microsoft Ignite and other conferences Access User Groups (AUG) webinars and local chapters (Chicago, Denver, Madrid, Hertfordshire, etc.) Access now included in most Office editions Included in nearly all (besides Online-only) editions Access in Office 365 Home, Personal, Business, Business Premium, ProPlus, E3, and E5 editions Access in Office 2016 Professional and ProPlus editions With MS Access having been added to most Office editions, presumably it will likewise be available with most Office 2019 editions now too. It's great to see these features available to Office 365 subscribers (or even sooner if opt-in for Insiders program) now being made available to others with Office 2019, and I look forward to the many more new advancements with Microsoft Access and Office to come. Links to More Info about Office 2019 You can find out more about Office 2019 with the following articles, FAQs and product pages: Office 365 vs. 2019 Editions Office 2019 Commercial FAQ Microsoft's Office 2019 Announcement Office 2019 and Discontinuing of Office 2016 The Verge release article ZDNet release article Endgadget release article VentureBeat release article TechSpot release article -- Dan Moorehead Founder & Chief Software Architect PowerAccess (www.PowerAccess.net) "Empower Microsoft Access – with new Tools | VBA Framework | PowerGit | Power Query-like PowerSQL | VSTO-like .NET API | CodeGen | Excel Formulas & Functions | Consulting | Excel ➜ Access ➜ SQL Conversion Tools"Solved411KViews8likes21CommentsRule using wildcard (or domain) for handling incoming emails
In line with the email security best practices recommended at Ignite this year, we are blocking our staff from using auto-forwarding rules in Outlook/Exchange Online. However there are valid scenarios where they need to know certain urgent emails have been delivered. We have many staff working for clients or partner companies in sensitive industries where they are not permitted to access Office 365 (or indeed any webmail service) while at work. What I want them to be able to do on their Office 365 email, account is something like: IF sender = *@importantclient.com THEN send notification to myemail@importantclient.com There are variations (perhaps include the subject line or from address in the notification, butt not the content), but that is the general idea. I can do it for fixed email addresses such as knownaccount@importantclient.com, but can't find any way for end users to do this for domains (@importantclient.com or *@importantclient.com) or other wildcards (from:managersname@*). I've tried in Outlook and Flow, but can't seem to make it work. I know it is possible with a Transport Rule, but I don't feel inclined to give my end user enough access to create these, for some strange reason.. Is this doable in O365 in any way (Outlook, Exchange, Flow, anything) in a way that normal (non-technical) users are likely to be able to handle? Thanks, Bob.312KViews0likes12CommentsShared mailbox: Use send-as, not send on behalf from Outlook 2016
Hello, We have a lot of shared mailboxes. For every shared mailbox, we create a specific security group that contains the members who should have access to that particular shared mailbox. We give full mailbox permissions and send-as permissions for that particular security group onto the shared mailbox. For example, security group A has full mailbox access and send-as permissions onto shared mailbox A. By adding users to security group A, they have full access to the shared mailbox. We create every new shared mailbox/security group combo using Powershell. That has been working flawlessly for the last years. However, for a recent new shared mailbox/security group combination, when a user that's member of the related security group wants to send an e-mail from the shared mailbox (by changing the from field in Outlook and selecting the shared mailbox from the global address list), Outlook tries to send every time 'send-on behalf'. This only happens for that newly created mailbox. I compared the output of Get-Mailbox and Get-RecipientPermission for the new problem shared mailbox and an older shared mailbox (which enable users to send mail send-as from outlook just fine) but I couldn't find any differences. For your information, that's the error we get back immediately after trying to do a send-as for the new shared mailbox: Your message did not reach some or all of the intended recipients. Subject: Test from Outlook Sent: 23/11/2017 9:27 The following recipient(s) cannot be reached: name of sending user on 23/11/2017 9:27 This message could not be sent. Try sending the message again later, or contact your network administrator. You do not have the permission to send the message on behalf of the specified user. Error is [0x80070005-0x0004dc-0x000524]. Why does Outlook always tries to do a send on behalf (what we don't want) where else for other shared mailboxes, send-as works fine? Using send-as from OWA however works just fine for the newest shared mailbox. It only seems a problem related to Outlook (tested on multiple clients that have access to the shared mailbox) and that particular new shared mailbox. Thanks in advance.Solved310KViews3likes12CommentsSharePoint Online hide "site contents" and "site usage" page (modern sites)
I have a scenario with external users. I created a custom permission level for these users. The custom permission level is a copy of the default "Read" permission level, but I unchecked the "View application pages" permissions. The external users are however still able to see the site contents page and, even worse, the 'site usage' page. I also activated the "Limited-access user permission lockdown mode" site collection feature. And I tried to work with limited access for external users, but then they don't have access at all. Is there a way to achieve what I want? A permission level where (external) users are not able to see site contents and site usage page? Thanks in advance!152KViews1like52CommentsOutlook - Certificate has been revoked
Hi all, not sure if anyone has experienced it, but we are getting tthis error multiple times a day when using outlook. It says : Outlook.office365.com Information you Exchange with this site cannot be viewed or changed by others. However, there is a problem with the sites security certificate. The security certificate for this site has been revoked, This site should not be trusted, If we dont click OK, outlook cannot send or receive emails. Sometime this window is hidden behind and therefor are not aware of it during the day. if we click view certificate, it looks legit and everything seems to be ok. If enter OWA, we get same certificate(according to thumbprint), but there is no warning or error, We have created a case with Exchange online team, but they say there are no error from their side and its internal network issue. We have cleared certificate revoke list from our DNS servers without any help. Any ideas on how to troubleshoot this further? We use Outlook 2016 with latest updates and have all mailboxes in Exchange online. I only have my archive mailbox attached to my outlook, Thanks!147KViews1like40CommentsMoving or Copying Files: Painfully Slow, Loss of Data
Hello All! Our company transitioned over to SharePoint Online about a year ago. One of the largest complaints I have to date, is the time it takes to move or copy files. In cases of one or two files, the time is minimal. But in cases where larger file moves are taking place - the pace of transfer is painfully slow. For example, today it took approx. 30 mins to transfer only 45.8 MB. Earlier this month, an employee spent the entire day waiting for files to transfer, only for her computer to stop responding, and have to re-start the entire process the next day. On our previous server based environment, the same transfer would take less than 30 minutes. Additionally, in some of these larger file moves, users have reported large losses of data. The files were moved, and confirmed, only to come in the next day and they have disappeared. This issue is decreasing adoption and causing our IT team multiple headaches. Any suggestions or helpful feedback?Solved122KViews2likes55CommentsUpdating SSL Certificate
Hello! I am trying to update our expiring SSL certificate and here is what I am following to do so: To Install an Intermediate Certificate in Microsoft Exchange Server 2016 Click Start, and then click Run.... Type mmc, and then click OK. The Microsoft Management Console (Console1) window opens. In the Console1 window, click File, and then select Add/Remove Snap-in. In the Add or Remove Snap-ins window, select Certificates, and then click Add. In the Computer Account window, select Computer Account, and then click Next. In the Select Computer window, select Local Computer, and then click Finish. In the Add or Remove Snap-ins window, click OK. In the Console1 window, click + to expand the Certificates (Local Computer) folder on the left. Right-click Intermediate Certification Authorities, mouse over All Tasks, and then click Import. In the Certificate Import Wizard window, click Next. Click Browse to find the intermediate certificate file. In the Open window, change the file extension filter to PKCS #7 Certificates (*.spc;*.p7b), select the *_iis_intermediates.p7b file, and then click Open. In the Certificate Import Wizard window, click Next. Select Place all certificates in the following store, and then click Browse. In the Select Certificate Store window, select Intermediate Certification Authorities, and then click OK. In the Certificate Import Wizard window, click Next. Click Finish. Click OK. Close the Console1 window, and then click No to remove the console settings. To Install an SSL Certificate in Microsoft Exchange Server 2016 Log in to the Exchange Admin Center. From the left menu, select Servers, and then click Certificates. Select your certificate (it has a “Pending request” status), and then click Complete. For File to import from, enter the certificate file path we provided (such as \\server\folder\coolexample.crt), and then click OK. Exchange installs your certificate. In the Certificates section, select your certificate again (the status changed to “Valid”), and then click Edit (pencil icon). Click Services, select the services to which the certificate applies (SMTP, UM, UM call router, IMAP, POP, and/or IIS), and then click OK. Your certificate is now ready to use with Exchange 2016. The issue I get is at the "pending certificate" does not show up in the list in EAS, just the original certificate still showing "expires on" as shown in the image. I have tried several times, verified that I am downloading the Exchange SLL, verified that it is for this particular server, restarted IIS etc etc. The server is on prem physical Windows 2016 Exchange server and there is only only one. Ideas? Thanks!120KViews0likes2Comments