Hello, Wiki Ninjas!
Today is Friday with International Community Update.
The end of July is as follows:
The topic of this month:
Thank you!!
Tomoaki Yoshizawa (yottun8)
Blog: blog.yottun8.com
Facebook: Tomoaki Yoshizawa
twitter: @yottun8
TechNet Profile: Tomoaki Yoshizawa
Using the SQL Server Migration Assistant (SSMA), Database Migrations to various Microsoft Database targets (SQL Server Versions on premise and cloud) are possible. One aspect of the migration is the mapping between source data types and target data types.
During an Oracle-2-SQL-Migration project, it was necessary to send the used Data Type Mapping to the customer.
The mapping is editable in SSMA on different levels, e.g. Default Project Settings, Project Level, Schema Level, Object Level and is separated into four types:
If possible, keep the mapping as simple as possible, not creating different mappings on different levels, e.g. BOOLEAN -> BIT on Project Level vs. BOOLEAN -> INT for a special Schema or even table or procedure.
There is currently no way to export the mapping within SSMA. In this blog post, I'll show how to export the Project Level Data Type Mapping to a tab separated file.
This blog post is based on SQL Server Migration Assistant for Oracle, Version 7.4. Other SSMA versions may work (slightly) differently.
The Data Type Mapping at the Project Level is accessible in SSMA by the menu item "Tools" -> "Project settings", tab "Type Mapping":
A single mapping may depend on the source precision, resulting in different data types and/or precisions (Button "Edit..."):
The mapping is stored in the file project-container.mappings, located in the root folder of the SSMA Project. The file is a XML file.
Sample (shortened to show all four types):
Using PowerShell and XSLT, the mapping could be transformed to tab separated values and stored as file:
$inputMapping = "project-container.mappings" $inputXsl = "ProjectMappings2TSV.xsl" $outputFile = "project-container.mappings.tsv" $xslt = New-Object System.Xml.Xsl.XslCompiledTransform; $xslt.Load($inputXsl); $xslt.Transform($inputMapping, $outputFile);
Mapping Oracle SQL-Server Arguments type mapping BFILE VARBINARY(MAX) Arguments type mapping BINARY_DOUBLE FLOAT[53] Arguments type mapping BINARY_FLOAT FLOAT[53] Arguments type mapping BINARY_INTEGER INT ... Columns type mapping BLOB VARBINARY(MAX) Columns type mapping CHAR CHAR ...Local variables type mapping CHAR CHAR Local variables type mapping CHAR[*..8000] CHAR[*] Local variables type mapping CHAR[8001..*] VARCHAR(MAX) ...Return values type mapping INT INT Return values type mapping INTEGER INT Return values type mapping LONG VARCHAR(MAX) ...
<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:msxsl="urn:schemas-microsoft-com:xslt" exclude-result-prefixes="msxsl"
>
<xsl:output method="text" indent="no"/>
<!-- Output: CSV with three columns, tab separated-->
<xsl:template match="/">
<xsl:text>Mapping Oracle SQL-Server
</xsl:text>
<xsl:for-each select="container/schema">
<xsl:variable name="MappingType" select="@type" />
<xsl:for-each select="mapping">
<xsl:value-of select="$MappingType" />
<xsl:text> </xsl:text>
<xsl:call-template name="PrintType">
<xsl:with-param name="TypeNode" select="source" />
</xsl:call-template>
<xsl:text> </xsl:text>
<xsl:call-template name="PrintType">
<xsl:with-param name="TypeNode" select="target" />
</xsl:call-template>
<xsl:text>
</xsl:text>
</xsl:for-each>
</xsl:for-each>
</xsl:template>
<!-- Print Type-->
<xsl:template name="PrintType">
<xsl:param name="TypeNode" />
<!-- either non-parametrized (without @) or parametrized-->
<xsl:choose>
<xsl:when test="contains($TypeNode/@type-id, '@')">
<xsl:value-of select="substring-before($TypeNode/@type-id, '@')" />
<xsl:for-each select="$TypeNode/*">
<xsl:text>[</xsl:text>
<xsl:choose>
<!-- Value exists => use value-->
<xsl:when test="@value">
<xsl:value-of select="@value"/>
</xsl:when>
<!-- Start and/or End exists => Interval {Start or *}..{End or *}-->
<xsl:when test="@start or @end">
<xsl:choose>
<xsl:when test="@start">
<xsl:value-of select="@start"/>
</xsl:when>
<xsl:otherwise>
<xsl:text>*</xsl:text>
</xsl:otherwise>
</xsl:choose>
<xsl:text>..</xsl:text>
<xsl:choose>
<xsl:when test="@end">
<xsl:value-of select="@end"/>
</xsl:when>
<xsl:otherwise>
<xsl:text>*</xsl:text>
</xsl:otherwise>
</xsl:choose>
</xsl:when>
<!-- No interval and also no value => * -->
<xsl:otherwise>
<xsl:text>*</xsl:text>
</xsl:otherwise>
</xsl:choose>
<xsl:text>]</xsl:text>
</xsl:for-each>
</xsl:when>
<!-- Non-parametrized => use type-id unmodified-->
<xsl:otherwise>
<xsl:value-of select="$TypeNode/@type-id" />
</xsl:otherwise>
</xsl:choose>
</xsl:template>
</xsl:stylesheet>
Many customers have asked how to disable "Microsoft Forms (Plan E3)" for all users via Windows PowerShell.
Claus Schiroky created a PowerShell script found here. This was originally created for Sway, but can be used for Forms. To use it, copy/paste the code to a .txt and rename the file extension to .ps1.
Before running this, you may need to install the prerequisites:
Microsoft Online Services Sign-In Assistant for IT Professionals RTW
Download and install enmsoidcli_64.msi
Azure Active Directory Connection
Download and install AdministrationConfig-V1.1.166.0-GA.msi
I named this ManageServices_Forms.ps1 and placed it in C:Temp. I then opened Windows PowerShell and browsed to that .ps1 and hit Enter.
Enter.
I then chose [21] DISABLE a service for all users > Enter
When asked for the AccountSkuId, I chose FORMS_PLAN_E3, because my use have Office 365 Enterprise E3 licenses:
I was then asked to enter my Microsoft Office 365 global admin email address > Enter.
I was then asked to enter the Service Plan name > Enter. I entered FORMS_PLAN_E3.
Unfortunately in my test environment my FORMS_PLAN_E3 ServicePlan in still in a PendingProvisioning State. So my test does show Forms as being Disabled. But trust me, this is now you do it.
Once my tenant in no longer in a PendingProvisioning state I will update the blog.
As mentioned in Demystifying "Dual Scan", configuring a combination of policies on Windows 10 1607 can result in those clients automatically [and unexpectedly] scanning against Windows Update, as well as subsequently ignoring deployment instructions from WSUS. We heard feedback from on-premises administrators that they needed the deferral policies only for ad hoc scans against Windows Update, a scenario which was not supported. The previous post mentioned a summer release of a policy on 1607 that would address the issue, and we are pleased to announce that this policy has arrived.
The package containing this policy is available today from KB4022723 (downloaded or imported from Catalog), and it will be part of the August cumulative update released to the WSUS channel (KB4025339) on 8/8/2017. After installing either of those updates, you will see this group policy under Windows Components/Windows Update:
New policy available in 1607 with the August cumulative update installed
How Dual Scan works with this policy
In order for Dual Scan to be enabled, the Windows Update client now also requires that the "Do not allow update deferral policies to cause scans against Windows Update" is not configured. In other words, if this policy is enabled, then changing the deferral policies in a WSUS environment will not cause Dual-Scan behavior. This allows enterprise administrators to mark their machines as "Current Branch for Business," and to specify that feature updates should not be delivered before a certain amount of days, without worrying that their clients will start scanning Windows update unbidden. This means that usage of deferral policies is now supported in the on-premises environment. While the new policy (dubbed "Disable Dual Scan") is enabled, any deferral policies configured for that client will apply only to ad hoc scans against Windows Update, which are triggered by clicking "Check online for updates from Microsoft Update":
How to use this policy
There are several relevant scenarios in your update management strategy. For the sake of completeness, here are the most common update management scenarios, updated for use with this policy:
Note that WSUS still ignores all deferral policies that have been configured, and that any deferral policies you do configure will only affect offering and download of updates for Microsoft products.
Coming soon
We prioritized getting this update out to the broadest install base. In parallel, we are porting the changes to 1703 (they are already in v.next). Disable Dual Scan is currently only for Group Policy at this time: MDM is also in the works, and will be delivered later this year.
Requirement
One of my customers recently came up with a requirement, where my customer wanted to get the People Picker Option while working with the Project Entity custom field using Project Online.
Based on my experience, it required a great amount of effort in order to customize the custom field to achieve this requirement. In addition, my customers have always configured it in Project Server on-premises product and not in Project Online application.
After doing a lot of research to achieve this requirement to configure People Picker for the Project Entity Custom Field, I learned that it can be done fairly easily using Project Details Pages and using a small Java Script.
Thanks to Laksh for sharing this information.
Steps to achieve the requirement
Below TechNet Gallery has the steps by step information, which is prepared and shared by James.
https://gallery.technet.microsoft.com/projectserver/Use-SharePoint-people-cc8289de
I hope this information helps you configuring People Picker in Project Online/Server easily.
Office Blogs や、元ネタの英語版の Office Blogs (英語) は、 新製品情報から、新機能や製品開発の背景まで、Microsoft Officeに関するさまざまな情報をお届けするブログです。ぜひブックマークして定期的にご参照ください！
過去のまとめを見るには、Office Blogs タグを参照してください。
製品についての最新情報まとめを見るには最新アップデートタグを参照してください。
I've always kept a fairly extensive home lab which I use for testing purposes. This lab started out as with Windows NT and had involved itself to Windows 2012 R2. A few lingering issues from over the years prompted me to rebuild my lab from the ground up recently, so I decided to document the journey. This prompted me to build upon my old "Home Lab Secrets" Series. This Series is the newer version of my original "Killer Home Lab" and leverages the use of the New Azure Portal. In addition to the New Portal, the lab has been restructured to minimize the amount of VM's needed within Azure to keep your Home Lab cost down, by leveraging azure or only Edge Services (Remote Desktop Gateway, OCSP, Mail Flow)
This new series will cover areas from the initial build out of an On-Premise Lab that is connected via VPN to an Azure Subscription all the way up to deploying an internet ready Exchange 2016 Server running in Hybrid Configuration Mode with Office 365. During this journey we will cover some of the technologies listed below:
In an effort to reduce SPAM comments and gauge future topics, I have decided to switch this blog to private. Details will flow soon.
Thanks,
Elliott
In an Exchange hybrid environment, there may times when you want to access both Exchange on-premises and Exchange Online mailbox attributes from within the same PowerShell session.
For example, let's say you want to create a report of all Exchange mailboxes that are on litigation hold, whether the mailbox is still in your on-premises Exchange or has been moved to Exchange Online. Now, Azure AD Connect does sync some mailbox hold-related attributes from on-premises AD to Azure AD including “msExchLitigationHoldDate”, “msExchLitigationHoldOwner” and “msExchUserHoldPolicies”. These are synced from on-premises mailbox-enabled users to corresponding Azure AD mail-enabled users. We could simply query recipient objects in Azure AD (Get-Recipient) where LitigationHoldEnabled is True but that would just be too easy. 
Querying mailboxes in both premises involves open a local Exchange PS session and then opening a remote Exchange Online PS session using the -Prefix switch on session import:
As you can see, I have used "O365" as the prefix on the Exchange Online cmdlets to distinguish between the two (you can use anything you’d like). Steps 3 and 4 simply pull on-premises and Exchange online mailbox data, respectively. If you wanted to combine the two queries, a simple example would be something like:
Now $mbxes holds a complete list of mailbox objects that have litigation hold enabled, both on-premises and in the cloud. There are lots of ways you could combine the data and report on it. This is just a very simple example and should give good direction on the capabilities.
There are also other uses for the -Prefix option such as when connecting to both Exchange Online and Security & Compliance Center remote PS sessions where there are overlapping cmdlets.
This one comes from collaboration with my colleague Brian Barrington.
Because of the issues with SCOM 2016 and the default APM modules impacting IIS and SharePoint servers….. (Read more about that issue HERE, HERE, and HERE)
Brian was looking for a way to easily remove the APM components from the deployed agents with minimal impact.
Normally, the guidance would be to uninstall the SCOM agent, then reinstall it from a command line installation using the NOAPM=1 command line parameter. That could be a challenging task if you have hundreds or thousands of agents!
His idea? Use my SCOM Agent Tasks MP here: https://blogs.technet.microsoft.com/kevinholman/2017/05/09/agent-management-pack-making-a-scom-admins-life-a-little-easier/
It has a class property in the state view called “APM Installed” to help you see which agents still have the APM components installed (which are installed by default)
It has a task called “execute any PowerShell”
In the task – Override to provide the command you want to run – such as:
msiexec.exe /fvomus "\servershareagentsscom2016x64MOMagent.msi" NOAPM=1
You just need to place the MOMAgent.msi file on a share that your domain computer accounts would have access to.
This performs a lightweight upgrade/installation of the agent, but only changes the switch “NOAPM=1” which will result in leaving all other settings alone, and only removing the APM service and components!
We have gotten good feedback on the success of this process across hundreds of agents in a short time frame.
Removing the APM MP’s
On another note – if you have no plans to use the APM feature in SCOM – you should consider removing those MP’s which get imported by default. They discvoer by default a LOT of instances of sites, services, and instances of classes where APM components are installed on the agents.
MP’s to remove in SCOM 2016:
All of the above can be deleted. However – in order to delete the Microsoft.SystemCenter.Apm.Infrastructure MP, you will need to remove a RunAs account profile association, then clean up the SecureReference library manually by deleting the reference.
In the Admin pane > Run As Configuration > Profiles, in the Data Warehouse Account. On the RunAs accounts, you will need to remove the Operations Manager APM Data Transfer Service:
Then – manually export the Microsoft.SystemCenter.SecureReferenceOverride MP, and edit it using your favorite XML editor. (Make a Backup copy of this FIRST!!!!!)
Delete the reference to the Microsoft.SystemCenter.Apm.Infrastructure MP.
Save this, then reimport the Microsoft.SystemCenter.SecureReferenceOverride MP.
At this point you can delete the final APM MP – Microsoft.SystemCenter.Apm.Infrastructure (Operations Manager APM Infrastructure)
Deleting that MP with manual edits too scary for you?
At a bare minimum – if you are not using the APM feature – you should disable the discoveries:
Then run Remove-SCOMDisabledClassInstance in your SCOM Command Shell, which will remove all these discovered instances that you don’t use.
(この記事は 2017 年 6 月 26 日にMicrosoft Partner Network blog に掲載された記事 6 Reasons Why Community Matters の翻訳です。最新情報についてはリンク元のページをご参照ください。)
昨今、ビジネスの世界で「コミュニティ」という単語を耳にする機会が増えました。パートナーシップ、共同作業、前向きな企業文化の形成が注目されるようになり、コミュニティの重要性はますます高まっています。私は長年コミュニティの構築に携わり、この仕事に情熱を注いできました。今回は、特にマイクロソフト パートナー ネットワークにとってコミュニティがなぜ、どのような点で重要なのか、私の見解をお話しします。
マイクロソフト パートナー ネットワーク ポッドキャストの最新エピソードでは、Rachel Braunstein と対談し、私にとってコミュニティとは何か、ビジネスにおいてコミュニティがなぜ重要なのかをお伝えしました。マイクロソフトのパートナー マーケティングおよびリクルーティング担当のシニア ディレクターとしての私の目標は、コミュニティの一体感を高め、パートナー様にそのメリットを実感していただくことです。パートナー様どうしが協力して、大きな相乗効果が生まれれば、こんなに嬉しいことはありません。コミュニティを通じて、すべてのパートナー様がより多くの成果を達成できるようにご支援いたします。
パートナー エコシステムを積極的に活用するべき 6 つの理由をご紹介します。
1. 仲間意識が高まる
コミュニティは、企業 (または個人) の間に一体感を作り出してくれるユニークなサポート ネットワークです。仲間としてつながり、受け入れられていると感じることは、個人の成長やスキルアップにきわめて重要です。仲間がいれば、リスクに臆せず新しいことにも挑戦でき、その結果、企業として、またはプロフェッショナルとしての成長につながります。
2.プロとして成長できる
コミュニティは、パートナー様が互いに学び合うことで、プロフェッショナルとして成長できるチャンスの場です。キャリアアップをサポートしてくれるメンターやインスピレーションを求めているなら、これほど最適なソーシャル グループは他にありません。
3.支え合える
パートナー コミュニティでは、パートナー様どうしが支え合います。お互いの抱える課題を共有し、他社の経験から学び、高め合うことで、それぞれのパートナー様のさらなる成長が見込めます。
4.リーダーシップを発揮できる
コミュニティ グループに参加すれば、業界の最前線に立ち、ソート リーダーとして活躍できる可能性が広がります。自身の経験から学んだ教訓を活かして、他のパートナー様がさらに多くの成果を達成できるようにアドバイスします。
5.専門知識が身に付く
コミュニティでは豊富な専門知識を得られます。パートナー エコシステムには、同じ業界の市場、製品、サービスに精通した企業やプロフェッショナルが集まるため、そのグループならではの専門的な情報交換が可能になります。
6.新たなビジネスを構築できる
パートナー様のコミュニティは、ビジネス エバンジェリストのコミュニティでもあります。共同マーケティングやクロスセルなど、パートナー ネットワークに参加する企業には無限のビジネス チャンスがもたらされます。他のパートナー様と協力して新しいソリューションやサービスを生み出せば、お互いの成果を拡大することができます。
マイクロソフト パートナー ネットワークの本質はコミュニティであり、Twitter、Facebook、LinkedIn などのソーシャル チャネルを通じて、他のパートナー様やマイクロソフトのスタッフとつながることもできます。業界をリードする仲間とつながり、アイデアを共有し、学ぶことができる、新しいマイクロソフト パートナー コミュニティ (英語) にぜひご参加ください。
コミュニティ構築の詳細については、マイクロソフト パートナー ネットワーク ポッドキャストの最新エピソードをご視聴ください。ポッドキャストを購読すると、最新のビジネスやテクノロジに関する業界のエキスパートやソート リーダーとの対談を毎週ダウンロードできます。また、過去のエピソードは iTunes、SoundCloud (英語)、iHeartRadio (英語)、Google Play Music、YouTube からダウンロードできます。
Welcome back for another analysis of contributions to TechNet Wiki over the last week.
First up, the weekly leader board snapshot...
As always, here are the results of another weekly crawl over the updated articles feed.
 |
Most Revisions Award Who has made the most individual revisions |
#1 M.Vignesh with 58 revisions.
#2 RajeeshMenoth with 54 revisions.
#3 Ken Cenerelli with 45 revisions.
Just behind the winners but also worth a mention are:
#4 Peter Geelen with 27 revisions.
#5 Arleta Wanat with 20 revisions.
#6 M.Qassas with 16 revisions.
#7 Ryen Kia Zhi Tang with 14 revisions.
#8 .paul. _ with 9 revisions.
#9 Abhishek Mishra - .Net, Azure PaaS, AI Architect with 9 revisions.
#10 Carsten Siemens with 7 revisions.
|
Most Articles Updated Award Who has updated the most articles |
#1 RajeeshMenoth with 40 articles.
#2 M.Vignesh with 33 articles.
#3 Ken Cenerelli with 22 articles.
Just behind the winners but also worth a mention are:
#4 Peter Geelen with 11 articles.
#5 Ryen Kia Zhi Tang with 7 articles.
#6 Carsten Siemens with 4 articles.
#7 Nourdine MHOUMADI with 3 articles.
#8 Abhishek Mishra - .Net, Azure PaaS, AI Architect with 2 articles.
#9 chilberto with 2 articles.
#10 Luiz Henrique Lima Campos [MVP] with 2 articles.
|
Most Updated Article Award Largest amount of updated content in a single article |
The article to have the most change this week was SharePoint: Delete item in List or Document Library using SPServices jQuery library, by Amit.AK.Kumar
This week's reviser was Peter Geelen
Nice article that explain how to delete item in SharePoint List or Document Library using SPServices jQuery library in SharePoint.
|
Longest Article Award Biggest article updated this week |
This week's largest document to get some attention is Windows Nano Server: Virtualization with VMware vSphere, by Ryen Kia Zhi Tang
This week's revisers were M.Vignesh & Ryen Kia Zhi Tang
Want to know how to deploy Windows Server 2016 Nano Server as a Virtual Machine in VMware vSphere virtualization platform, read this article, very informative
|
Most Revised Article Award Article with the most revisions in a week |
This week's most fiddled with article is TechNet Guru Competitions - August 2017, by Peter Geelen. It was revised 12 times last week.
This week's revisers were JimmySal, .paul. _, [Kamlesh Kumar], Asfaw Ayele(MCTS, MCP), Peter Geelen & SYEDSHANU - MVP
August Guru competition live and we are searching you Gurus!! Go Go Gurus!!
|
Most Popular Article Award Collaboration is the name of the game! |
The article to be updated by the most people this week is SharePoint Governance Planning, by Asfaw Ayele(MCTS, MCP)
Very nice article Asfaw, if anyone wants to know SharePoint Governance Planning, read this article
This week's revisers were Peter Geelen, RajeeshMenoth, M.Vignesh, Richard Mueller & Asfaw Ayele(MCTS, MCP)
|
Ninja Edit Award A ninja needs lightning fast reactions! |
Below is a list of this week's fastest ninja edits. That's an edit to an article after another person
Congratulations to [Kamlesh Kumar]!
Also in the top ten are:
|
Winner Summary Let's celebrate our winners! |
Below are a few statistics on this week's award winners.
Most Revisions Award Winner
The reviser is the winner of this category.
M.Vignesh
M.Vignesh has won 8 previous Top Contributor Awards. Most recent five shown below:
M.Vignesh has not yet had any interviews, featured articles or TechNet Guru medals (see below)
Most Articles Award Winner
The reviser is the winner of this category.
RajeeshMenoth
RajeeshMenoth has won 17 previous Top Contributor Awards. Most recent five shown below:
RajeeshMenoth has TechNet Guru medals, for the following articles:
RajeeshMenoth has not yet had any interviews or featured articles (see below)
Most Updated Article Award Winner
The author is the winner, as it is their article that has had the changes.
Amit.AK.Kumar
Amit.AK.Kumar has won 2 previous Top Contributor Awards:
Amit.AK.Kumar has not yet had any interviews, featured articles or TechNet Guru medals (see below)
Longest Article Award Winner
The author is the winner, as it is their article that is so long!
Ryen Kia Zhi Tang
Ryen Kia Zhi Tang has been interviewed on TechNet Wiki!
Ryen Kia Zhi Tang has won 6 previous Top Contributor Awards. Most recent five shown below:
Ryen Kia Zhi Tang has TechNet Guru medals, for the following articles:
Ryen Kia Zhi Tang has not yet had any featured articles (see below)
Ryen Kia Zhi Tang's profile page
Most Revised Article Winner
The author is the winner, as it is their article that has ben changed the most
Peter Geelen
Peter Geelen has been interviewed on TechNet Wiki!
Peter Geelen has featured articles on TechNet Wiki!
Peter Geelen has won 183 previous Top Contributor Awards. Most recent five shown below:
Peter Geelen has TechNet Guru medals, for the following articles:
Most Popular Article Winner
The author is the winner, as it is their article that has had the most attention.
Asfaw Ayele(MCTS, MCP)
This is the first Top Contributors award for Asfaw Ayele(MCTS, MCP) on TechNet Wiki! Congratulations Asfaw Ayele(MCTS, MCP)!
Asfaw Ayele(MCTS, MCP) has not yet had any interviews, featured articles or TechNet Guru medals (see below)
Asfaw Ayele(MCTS, MCP)'s profile page
Ninja Edit Award Winner
The author is the reviser, for it is their hand that is quickest!
[Kamlesh Kumar]
[Kamlesh Kumar] has been interviewed on TechNet Wiki!
[Kamlesh Kumar] has won 19 previous Top Contributor Awards. Most recent five shown below:
[Kamlesh Kumar] has TechNet Guru medals, for the following articles:
[Kamlesh Kumar] has not yet had any featured articles (see below)
[Kamlesh Kumar]'s profile page
Another great week from all in our community! Thank you all for so much great literature for us to read this week!
Please keep reading and contributing!
Best regards,
— Ninja [Kamlesh Kumar]
The EMS Documentation team have been releasing updating a few things over on the TechNet Gallery, here are some that I thought would be worth highlighting for the OEM and System Builder community.
Infographic: Simplify Windows 10 management and lower TCO with EMS
Windows has evolved. Simplify Windows 10 management and lower the Total Cost of Ownership (TCO) with the Microsoft Cloud. See how Enterprise Mobility + Security (EMS) and Windows 10 can be used together to ease procurement, simplify provisioning and lower TCO through modern management & security, and deliver cloud-based updates without the need for an on-premises infrastructure.
Infographic: Management choices with Microsoft Intune.
In a complex device landscape, you need choices. Microsoft Intune gives you the flexibility and control to secure your data on any device--even those you don't manage.
Infographic: Manage Intune with the Azure portal and Graph API
One console. One set of APIs. Limitless possibilities. Intune offers you more flexibility than ever before to manage and secure your enterprise.
Welcome everyone to our Sunday's surprise blog post. Everyone around in a software house talks about performance that might be your manager, client, senior or might be your architect. Performance make significant impact to our software systems and has a lot to do with client satisfaction. If we talk about web solutions, they need to be fast. Most of us would like amazing and fast web experience regardless of aspects like,
But in real world it happens rarely, the reason is that we cache static content using CDNs (Content Delivery Network) but what about dynamic data? How about a service which is returning dynamic data? In this case a question arrives that how would you sort out which dynamic data, what services a user would interact with that need to be cached? Well, Microsoft Azure has solved the problem.
With Azure CDN Dynamic Site Acceleration (DSA), the performance of web pages with dynamic content is significantly improved. DSA includes a variety of techniques that benefit the latency and performance of dynamic content. According to Microsoft’s official blog, here are some of the salient features of DSA,
Looking at the features above it looks like that if we get these features that would be all that we need to make over web app’s response super-fast. It all starts with Network and TCP optimizations. Origin is a very important constraint when we talk about CDN, with DSA it enables to dynamically find fastest and the most reliable path to your origin to retrieve and deliver dynamic content and it’s being constantly evaluated.
Not only this, but it also optimizes TCP by keeping connections open and reusing them for additional request it accelerates connection setup, transmission rate and reduce packet loss. But what about dynamic prefetching?
Well, that’s the most amazing part of DSA, based on user behavior and access patterns the CDN learns which assets are required by the application and preemptively fetched content from the origin and brings it closer to the user for blazing fast experience. The DA also enables adaptive image compression, which is continuously monitored with respect to internet conditions.
In a nutshell, it’s a super step by Azure CDN that they introduced DSA which would enable tech companies provided amazing experience and blazing fast delivery of not only static but also dynamic content.
In case you would like to learn more about it though video, you may follow the link.
I hope you liked it, will come up with another post, another day. Happy Sunday!
Wiki Ninja – Saad Mahmood
Bu yazıda SCCM üzerinden dağıtılmak üzere bir imaj nasıl hazırlanır bunu anlatmaya çalışacağım.
İmaj konusunda hereksin bir tarzı ve yöntemi vardır. Bu yazıda anlatıldığı gibi yapmamanız sizin yanlış yaptığınızı göstermez. Benim anlatımımda tek ve mutlak doğru olan yöntem olmayabilir. Önemli olan ortamınızda sorunsuz ve kararlı çalışan bir yöntemi belirleyerek kullanmanızdır.
Ben işe genellikle Hyper-V üzerinden bir sanal sunucu oluşturarak başlarım. VmWare üzerinden de oluşturabilirsiniz. Tek dikkat ettiğim husus sanal sunucunun Legacy Bios kullanmasıdır. Bu yüzden Hyper-V üzerinden Generation 1 ile ilerlemenizi öneririm.
Fiziksel bir bilgisayarı tercih etmemenin sebebi o bilgisayara ait sürücülerin bir şekilde imajımın içinde kalmasını istemememdir. Ayrıca sanal da işlerin daha hızlı olması ve snapshot almak gibi güzelliklerden faydalanabilme imkanını olmasını da büyük bir avantaj.
İmaj hazırlık işlemlerinde ilk adımda dikkat ettiğim şey disk formatlama ekranı. Bu ekranda sistem için ayrılan alanı SCCM'den dağıtımında kullanacağımız Task sequence'den ayarlayabildiğimiz için burada oluşmasını istemiyorum.
Bunu içinde aşağıdaki işlemleri yapıyorum.
İşlem sonunda aşağıdaki gibi tek partition' dan oluşan bir disk elde etmiş olduk.
Kurulum tamamladığımda bizi aşağıdaki ekran karşılıyor. Bu ekran Windows 10 Build 1703'e ait. Önceki sürümlerde daha farklı bir ekran geliyordu.
Bu ekranda hiçbir işlem yapmadan CTRL+SHIFT+F3 tuşlarına basarak sistemin Audit Modunda açılmasını sağlıyoruz. Bu tuş kombinasyonu tüm Windows işletim sistemlerinde kullanılabilir.
Sistem bu tuşlara bastığınız anda reboot olacak ve Administrator kullanıcısı ile otomatik olarak oturum açılacaktır. Oturum açıldığında sizi aşağıdaki ekran karşılar. Her reboot işleminde bu ekran çıkar ve siz her defasında iptal tuşuna basmalısınız. Birden fazla kez reboot etmeniz ya da sistemi shutdown etmenizde sakınca yok, sadece aşağıdaki resimde görünen Tamam butonuna basmayın
Ben genelde ihtiyaç duyulduğu için imajımın içine .NET 3.5 kurulumunu yapıyorum. Sizin de ihtiyacınız varsa aşağıdaki şekilde işletim sistemi DVD'si takılıyken kurulum yapabilirsiniz.
dism.exe /online /enable-feature /all /featurename:NetFX3 /Source:D:sourcessxs /LimitAccess
Yine tercihi size bırakarak dilerseniz kullanmak istediğiniz Office sürümünü de imaja kurulum süresini azaltmak adına ekleyebilirsiniz.
İmaja Office de eklemek isteyenlere tavsiyem kurulumu aşağıdaki şekilde yapmalarıdır. Office DVD'sini takıp kurulum yaptığınızda Office KMS üzerinde aktive olmama gibi sorunlar yaşayabilirsiniz. Bir diğer ipucu da Office kurulumundan sonra nasıl güzel yüklenmiş mi diye herhangi bir Office bileşenini (Word, Excel vbg) tıklayıp açmayın. Bu durumda aktivasyon sorunlarına neden olabiliyor.
Bilgi: Aşağıdaki şekilde hazırladığınız Office paketini SCCM üzerinden de dağıtmak için kullanabilirsiniz.
Öncelikle Office DVD içeriğiniz imaj alacağınız sistemde bir klasör içine kopyalayın.
Daha sonda CMD'yi Run as Admin olarak açarak setup.exe / admin komutu ile Office Customization aracını çalıştırın.
Aşağıdaki adımlar en sık kullanılan ayarlardır. Her resim için açıklama yazmayacağım resimlerden neleri özelleştirdiğimi anlayabilirsiniz. Sizlerde kendinize göre özelleştirmeler yapabilirsiniz.
Aşağıdaki resim için önerim kullanın ya da kullanmayın ilk olarak en tepeden "Run all from My Computer" seçeneğini seçin.
Daha sonra aşağıdaki gibi kullanmak istemediğiniz bileşenleri kaldırın. Burada Skype Kurumsal kullanacaklar için bir uyarı ne olursa olsun Skype kurumsal başlığını tıklayın ve "Installed on First Use" seçeneğini seçin. Bunu yapmazsanız Skype Kurumsal kurulmayacaktır
Masa üstü ya da Start Menüde Office ürünlerinin kısa yollarının olmasını isterseniz aşağıdaki gibi eklemeler yapabilirsiniz. Buradaki ipucu da Start in alanına [ işaretini koymak zorundasınız yoksa ekran kapanmaz ve hata verir.
Bu konu ile ilgili kaynak: http://support.microsoft.com/kb/2797938
İşlerimiz bittikten sonra ayarlarımızı Office dosyalarını kopyaladığımız klasörün içine kaydediyoruz.
Artık Office imaj içine kurulmak için hazır. CMD "Run as Admin" olarak açılır ve aşağıdaki komut ile kurulum başlanır.
Kurulum ekranı çıkmayacağı için Task Manager üzerinden setup.exe kaybolana kadar bekleyiniz.
Kurulum bittikten sonra C:Office2016 klasörünü silmeyi ve geri dönüşüm kutusunu boşaltmayı unutmayınız. İmajın içinde bu klasörün kalmasını istemeyiz.
Ben genelde imaj içine başka yazılım kurmayı tercih etmiyorum. Kurmak istediğim programları Task Sequnce üzerinden yükletiyorum.
Ancak isteyenler istedikleri kurulum ve özelleştirmeleri yapabilirler.
Uyarı: İmaj içine SCCM ajanı ya da Anti-Virüs yazılımı kurulum yapmamanızı öneririm.
Şimdi imajımızın tüm Windows Update'lerini yapabiliriz.
Bu ekranda ki hatırlatmam da aşağıdaki resimden "Gelişmiş Seçenekler" bağlantısını kullanarak diğer Microsoft ürünlerinin de güncellemelerinin alınmasını sağlayacak kutucuğu işaretlemeniz yönünde olacak.
Güncellemelerin yüklenmesi de bittiğinde sistemi birkaç kez reboot edin ve tekrar Windows Update kontrolü yapın Gözden kaçan olmasın.
Artık imajı almak için hazırız. SCCM konsoluna giderek imaj alma CD'sini (capture cd) oluşturalım.
Capture CD de hazır. Bu noktada ilerlemeden önce imajını alacağınız sanal sunucuyu kapatıp snapshot almanızı tavsiye ederim.
İmajını alacağımız sanal sunuya Windows açıkken Capture CD sini takın ve Autorun ile ilerleyin. Kaçıranlar aşağıdaki şekilde başlatabilirler.
Ben imajımı yukarıdaki resimde görüldüğü üzere ağ üzerinden SCCM sunucusuna ya da müsait olan bir sunucu üzerine alıyorum. Sanal sunucuya ikinci bir HDD takıp imaj almayı pek sevmiyorum.
Neden derseniz bu tip disk ya da partitionlar (işletim sistemini kurarken sistem bölümünü de bu sebepten oluşturmamıştık) aşağıdaki resimdeki image index alanında 1-1 – 2-2 – 3-3 şeklinde görünmesine sebep oluyor. Buda sadece C sürücüsüne format atalım D sürücüsü ne dokunulmasın dediğiniz senaryolarda sizi uğraştırabilir.
İmaj alma işlemi tamamlandıktan sonra imajımızı SCCM konsolundan eklememiz ve istediğimiz DP'lere göndermemiz gerekli. Task sequence üzerinden de gerekli ayarlamaları yaptıktan sonra her şey tamamdır.
One of the scenarios we are often asked about at the events we support is "why are my Windows 10 clients going to Windows Update instead of WSUS?", and previously I've pointed people to the Demystifying "Dual Scan" post from the WSUS Product Team Blog. They've just put up a new post Improving Dual Scan on 1607 which is being released as part of the August cumulative update.
This update is also being rolled into 1703, and is already part of 1709. Right now the support is for Group Policy, with MDM support coming later this year. Jump to their blog post to get the full details of this update, but here's their description of how dual scan works with this policy...
In order for Dual Scan to be enabled, the Windows Update client now also requires that the "Do not allow update deferral policies to cause scans against Windows Update" is not configured. In other words, if this policy is enabled, then changing the deferral policies in a WSUS environment will not cause Dual-Scan behavior. This allows enterprise administrators to mark their machines as "Current Branch for Business," and to specify that feature updates should not be delivered before a certain amount of days, without worrying that their clients will start scanning Windows update unbidden. This means that usage of deferral policies is now supported in the on-premises environment. While the new policy (dubbed "Disable Dual Scan") is enabled, any deferral policies configured for that client will apply only to ad hoc scans against Windows Update, which are triggered by clicking "Check online for updates from Microsoft Update"
They then go on to discuss five of the common update management scenarios, and how they should be updated for use with this policy...
Windows updates from WU, non-Windows content from WSUS
Windows updates from WSUS, blocking WU access entirely
Windows updates from WU, not using WSUS at all
Windows updates from WSUS, supplemental updates from WU
Windows updates from Configuration Manager, supplemental updates from WU
法人向け無料会員制情報提供サービス MSBC (Microsoft Business Connection) は、皆様より格別なご厚情を賜り今日までご利用いただいてまいりましたが、2017 年 9 月 29 日 (金) をもちまして、サービスを終了させていただくこととなりました。 今後の MSBC 終了までのスケジュール、および今後のマイクロソフト製品やサービス、キャンペーンなどについての情報につきましては、こちらから詳細をご覧ください。
こんにちは、SharePoint サポート 西村です。
今回はお問い合わせいただくことも多い、SharePoint で使用できるブラウザーについて投稿いたします。
SharePoint でサポートされているブラウザーは、下記公開資料に記載のとおりです。
Internet Explorer (IE) 以外の Google Chrome や FireFox 等も最新リリース バージョンであればサポートされます。
タイトル：SharePoint Server 2016 でのブラウザー サポートの計画
アドレス：https://technet.microsoft.com/ja-jp/library/cc263526(v=office.16).aspx
しかしながら、エクスプローラー表示や、Skype のプレゼンスの表示等、一部の ActiveX コントロールを使用する機能については、上記資料にも記載のとおり 32 ビット バージョンの IE のみで利用することが出来ます。
---- 一部抜粋 ----
SharePoint Server 2016 の機能によっては ActiveX コントロールを必要とするものがあります。したがって、ActiveX をサポートしないブラウザーでは使用できる機能が制限されます。現在、この機能をサポートするのは 32 ビット バージョンの Internet Explorer のみです。
---- 一部抜粋 ----
64 ビットのクライアントも一般的となっている昨今、わざわざ 32 ビットのアプリケーションを使わないといけないの？と思われる方もいらっしゃるのではないでしょうか。
ご安心ください。一般的な SharePoint の利用環境においては、64 ビット クライアントをご利用のユーザーの方に特に意識していただく必要もなく、通常は ActiveX コントロールが利用できる状態となっています。
IE8 以降 LCIE という機能が導入され、ウィンドウのアドレス バーやお気に入りバーが表示される部分を処理するフレーム プロセスと、コンテンツが表示される部分を処理するコンテンツ プロセスの2 種類のプロセスに分かれて動作するようになりました。
タスクマネージャーで確認いただくと、開いているタブの数だけ iexplorer.exe のプロセスが起動しているのをご確認いただけるかと思います。
64 ビット OS 上の動作は、IE9 までは Program Files 配下の iexploere.exe を起動すれば、フレーム プロセス、コンテンツ プロセスともに 64 ビット、 Program Files (x86) 配下の iexplorer.exe を起動すれば、フレーム プロセス、コンテンツ プロセスともに 32 ビットで動作し、「64 ビット版の IE」、「32 ビット版の IE」が独立して存在していたため、SharePoint の ActiveX コントロールを機能させるためには、「32 ビット版の IE」をご利用いただく必要がありました。
IE10 以降では、64 ビット OS の場合マネージ プロセスは 64 ビット、コンテンツ プロセスは 32 ビットで動作するよう変更されたため、通常通り SharePoint サイトを閲覧する限りでは IE は 32 ビットとして動作し、ActiveX コントロールも問題なく利用することが可能です。
コンテンツ プロセスも 64 ビットで動作させたい場合には、インターネット オプションの詳細設定タブにて、"拡張保護モードで 64 ビット プロセッサ" を有効にする" の設定を明示的に行い、保護モードが有効なページを表示する必要があります。
なおエクスプローラー ビューを使用する際は、SharePoint サイトの URL を信頼済みサイトに登録する必要がありますので、基本的には信頼済みサイトとして SharePoint にアクセスされている方が多いのではないかと思います。
信頼済みサイトの既定の設定では保護モードは無効です。
上述の IE の動作、拡張保護モードの動作については IE サポート チームのブログに詳細が投稿されておりますので、こちらも是非ご参照ください。
タイトル：Internet Explorer 11 のプロセスの動作について (LCIE)
アドレス：https://blogs.technet.microsoft.com/jpieblog/2016/07/29/internet-explorer-11-lcie/
タイトル：IE10 & IE11 : 拡張保護モードの実態
アドレス：https://blogs.technet.microsoft.com/jpieblog/2013/11/29/ie10-ie11/
今回の投稿は以上です。
本記事は、Microsoft Security Response Center のブログ “Announcing the Windows Bounty Program” (2017 年 7 月 26 日 米国時間公開) を翻訳したものです。
Windows 10 は世界に誇る軽減策を搭載し、私たちのセキュリティに対する精力的な取り組みを象徴する最高で最新の製品です。マイクロソフトのソフトウェア セキュリティを改善する長年にわたる戦略の 1 つとして、攻撃者が脆弱性を特定し悪用することを困難かつコストのかかる行為にするための、防御技術への投資が挙げられます。システムのセキュリティを強化するために、DEP、ASLR、CFG、CIG、ACG、Device Guard、および Credential Guard などの軽減策や防御策を組み込み、Windows Defender Application Guard のような防御機能を引き続き追加することで、シームレスなカスタマー エクスペリエンスを保証しながらエントリー ポイントの保護を大幅に強化していきます。
Windows のセキュリティ水準を高く保つ方針のもと、2017 年 7 月 26 日に Windows に関する報奨金プログラムを開始します。このプログラムは Hyper-V、軽減策バイパス、Windows Defender Application Guard、および Microsoft Edge の重点分野に加え、Windows Insider Preview のすべての機能を対象とします。また、Hyper-V のバグ報奨金プログラムに関しては、報奨金の支払い額の範囲を拡大します。
2013 年以来、私たちはさまざまな Windows 機能に関する複数の報奨金プログラムを実施しています。セキュリティは常に変化しており、異なる時点で異なる種類の脆弱性を優先します。マイクロソフトはバグ報奨金プログラムに高い価値があると確信し、私たちのセキュリティ機能の拡張に役立つと信じています。
プログラムの概要は、以下のとおりです。
| カテゴリ | 対象 | Windows のバージョン | 報奨金の範囲 (米国ドル) |
| 重点分野 | Microsoft Hyper-V | Windows 10
Windows Server 2012 Windows Server 2012 R2 Windows Server Insider Preview |
$5,000 から $250,000 |
| 重点分野 | 軽減策バイパスおよび防御策 | Windows 10 | $500 から $200,000 |
| 重点分野 | Windows Defender Application Guard | WIP slow | $500 から $30,000 |
| 重点分野 | Microsoft Edge | WIP slow | $500 から $15,000 |
| 基本 | Windows Insider Preview | WIP slow | $500 から $15,000 |
マイクロソフト報奨金プログラムの最新情報は、こちらの Web サイトおよび関連規約や FAQ を参照してください。
Akila Srinivasan、Joe Bialek、Matt Miller - Microsoft Security Response Center
David Weston、Jason Silves - Windows and Devices Group Enterprise and Security
Arthur Wongtschowski、Mary Lee、Ron Aquino、Riley Pittman - Windows and Devices Group Information Security
■ご報告時の注意点
マイクロソフトの報奨金プログラムへご参加される場合は、脆弱性報告はすべて、こちらのガイドラインに沿って米国 secure@microsoft.com へ直接ご報告いただく必要があります。この際、英語でのご報告が困難な場合は日本語の併記・記載でも構いません。これは、報奨金受賞者選定において、公平性の観点で重要となります。皆様のご参加をお待ちしています！
■関連情報
今月のマイクロソフト製品条項（PT）改定により、"Windows 10 on 認定クラウド" が正式に許諾されるようになりました。これまでも当ブログにて関連情報をお伝えしてきましたが、多くのお問い合わせをいただいていますので改めて現状をまとめてご案内します。
■ まとめると…
以前の記事（Windows 10 on Azure の現状について as of 2017.04）にてご案内の通り、これまで Windows 10 をはじめとする "Windows デスクトップ オペレーティング システム" は、Azure をはじめとするマルチテナント型ホスティング環境で利用することは認められていませんでした。
2017年8月付のマイクロソフト製品条項改定により、一定の条件を満たす場合に Microsoft Azure および 認定を受けたマルチテナント ホスティング パートナー (QMTH, 詳細は後述) で Windows 10 を稼働することが認められるようになりました。
■ マイクロソフト製品条項の改定
本改訂は、マイクロソフト製品条項（PT）にて明記されています。具体的には、8月1日付のPT (p.45) にて下記文言が追加されており、これが "Windows 10 on クラウド" 許諾の根拠となります。
3.5 Windows 10 マルチテナント ホスティング
Azure AD ベースのライセンス認証を使用する、Windows 10 Enterprise E3/E5 または VDA E3/E5 Per User SL をお持ちのお客様は、Windows 10 Creators Update 以降の Current Branch ソフトウェアを、Microsoft Azure 上で実行されている仮想マシン、または対象となるマルチテナント ホスティング パートナー (www.microsoft.com/Qualified_MultiTenant_Hoster_Program に規定) との共有サーバーにインストールすることができます。ライセンスを取得した各ユーザーは、本ソフトウェアの最大 4 つのインスタンスにアクセスすることができます。
Microsoft Azure 上でイメージを構成する場合、お客様は、そのマルチテナント ホスティングの使用が Windows 10 に対するものであることを示し、https://docs.microsoft.com/en-us/windows/deployment/windows-10-enterprise-activation-subscription に掲示されるその他のソフトウェア構成要件に従う必要があります。これには、Azure Virtual Machines のコストは含まれません。パートナー ベースのデプロイ要件は、www.microsoft.com/Qualified_MultiTenant_Hoster_Program で確認できます。
なお製品条項は毎月更新されていますので、常に最新版をご確認ください。
■ 何ができるようになったか？
製品条項に記載の情報がすべてですが、NG 例も交えながら、もう少しかみ砕いてみます。
最後のプラットフォーム部分ですが、ライセンス管理などを適切に実施いただける環境である必要があるため、QMTH という認定制度を取っています。（QMHT のリストに掲載されていないクラウドで動かすことは、引き続きライセンス上認められません）。
QMTH パートナーのリストはこちらになります。ただし今日（8/7）時点では最新化が追い付いていないようですので、もうしばらくお待ちください。なお Office 365 も同じような制度を採用しており、日本では IIJ 社および NTT コミュニケーションズ社が認定を受けています。
■ Windows 10 on Azure での考慮点
以上より、適切なライセンスをお持ちの場合は Windows 10 on Azure (BYOL) が許諾されています。ただし、まだ環境面での整備など追い付いていないところがありますのでご注意ください。
ライセンスに関してはケースに応じて解釈が難しい場合も出てくるかと思います。
ご不明な点や迷われる点がある場合は、（意図せずライセンス違反にならないためにも）マイクロソフトのライセンス窓口や担当営業、ライセンスパートナー様にご相談ください。
こんにちは、SharePoint サポートの小松です。
今回は、OneDrive for Business で共有設定したアイテムが共有相手のページに表示される条件について記載いたします。
<目次>
以下の各ページで表示されるアイテムについてご説明します。
1. [自分と共有] ページ
2. 別ユーザーの OneDrive for Business ページ
3. [ファイル] ページ (下側)
4. 共通のドキュメント (従来の UI)
5. XXX のドキュメント (従来の UI)
1. [自分と共有] ページ
[自分と共有] ページでは共有相手として自分 (ログイン ユーザー、図1の場合は user01) が設定されているアイテムが表示されます。
ユーザー自身を共有相手として設定する必要があるため、セキュリティ グループや “すべてのユーザー” で共有設定されたアイテムは表示されません。
図1. [自分と共有] ページ
2. 別ユーザーの OneDrive for Business ページ
ログイン ユーザー以外のユーザーの OneDrive for Business ページを表示した場合、別ユーザーの OneDrive for Business 上のドキュメントのうち、ログイン ユーザーに閲覧または編集権限のあるアイテムが表示されます。
階層構造で表示されるため、表示中の URL のルート フォルダー配下のフォルダーに含まれるアイテムは表示されません。
例えば、ログイン ユーザーの OneDrive for Business ページから [自分と共有] ページにアクセスし、表示された任意のフォルダーをクリックした場合、フォルダーの所有者の OneDrive for Business のアイテム画面 (図 2) に遷移します。（URL が folder1 の所有者である user02 の OneDrive for Business サイトになります。）
この画面では、user02 が user01 に共有したフォルダー (folder1) のうち、user01 に閲覧または編集権限のあるアイテムが表示されます。
図2. 別ユーザーの OneDrive for Business ページ
3. [ファイル] ページ （下側）
モダン UI でログイン ユーザー以外のユーザーの OneDrive for Business ページを表示した場合、画面左に 2 つの [ファイル] リンクが表示されます。
ファイル (上側) (英語表記では [Files] と表示) は、”2. 別ユーザーの OneDrive for Business ページ” となります。
ファイル (下側) (英語表記では [Our Files] と表示) をクリックした際に表示されるページでは、現時点では以下の条件を満たすアイテムが表示されます。
- 画面左上に表示されているユーザー (図3 の場合は user02) がログイン ユーザー (図3 の場合は user01) に共有したアイテム
[ファイル] ページ (下側) では、フォルダの階層構造に関係なく、上記の条件を満たす、すべてのアイテムが表示されます。
図3. [ファイル] ページ （下側）
4. 共通のドキュメント (従来の UI)
[共通のドキュメント] には、以下の条件を満たすアイテムが表示されます。
- 画面上部に表示されるユーザー (図4 の場合は user02) がログイン ユーザー (図4 の場合は user01) に共有したアイテム
- ログイン ユーザーが画面上部に表示されるユーザーに共有したアイテム
- あるユーザーがログイン ユーザーと画面上部に表示されるユーザーの両方に共有したアイテム
個別のユーザーを共有相手として設定した際に上記条件が満たされる必要があります。そのため、セキュリティ グループや "すべてのユーザー" への共有設定で上記の条件を満たす場合は、対象アイテムは表示されません
また、[共通のドキュメント] では、フォルダの階層構造に関係なく、上記の条件を満たす、すべてのアイテムが表示されます。
図4. 共通のドキュメント (従来の UI)
5. XXX のドキュメント (従来の UI)
[XXX のドキュメント] では、画面上部に表示されるユーザー (図5 の場合は user02) のドキュメント (Documents/Forms/All.aspx) のうち、ログイン ユーザー (user01) に共有されているアイテム（フォルダーおよびファイル）が表示されます。
OneDrive for Businessドキュメントのルートフォルダー (Documents/Forms/All.aspx) 配下のフォルダー ("ルートフォルダー/folder1") 内のアイテムは表示されません。
今回の投稿は以上になります。
本情報の内容（添付文書、リンク先などを含む）は、作成日時点でのものであり、予告なく変更される場合があります。
