If you got errors uninstalling Windows phone software and you are prompted to insert path about this msi:
{256BFC36-34DF-4C3E-8051-5DDCC16B9334}v1.1.2726.0.msi
Solution can be found repairing Install and uninstall Windows feature with Fix.It tool.
Here is relative link.
https://support.microsoft.com/en-us/mats/program_install_and_uninstall?wa=wsignin1.0
Here is Windows phone download link:
https://www.windowsphone.com/en-US/How-to/wp8/windows-phone-app-for-desktop
Wsus - Choose your best WSUS architecture
Here they are two official Microsoft Guide to explain you all options to better determine your company wsus infastructure.
here they are some options:
1. Th ere is possibility to define an upstream server where approve patch and replicate to downstream servers. In this case you can decide, to preserve mpls connectivity, to download patch with local internet withouth downloading them from upstream server.
· Using the BranchCache feature:
BranchCache is a new feature in Windows 7 and Windows Server 2008 R2 that reduces
WAN link utilization and improves application responsiveness. To enable BranchCache
acceleration of content served by the WSUS server, install the BranchCache feature on the
server and the clients, and ensure that the BranchCache service has started. No other steps
are necessary. For information about installing BrancheCache, see the BranchCache Early
Adopter's Guide (http://go.microsoft.com/fwlink/?LinkId=148741).
· Branch offices with low-bandwidth connections:
In some organizations, branch offices have low-bandwidth connections to the central office
but high-bandwidth connections to the Internet. In this case you may want to configure
about how to set up this kind of configuration, see Advanced Synchronization Options.
If you have many mobile users who log on to your network from different sites, you may want to use the following configuration to allow them to update their computers from the closest WSUS server. In this configuration, shown in the "Roaming Clients Using Different WSUS Servers" illustration below, there is one WSUS server per region, and each region is a DNS subnet. All clients are pointed to the same WSUS server name, which resolves in each subnet to the nearest WSUS server. See Appendix D: Configure WSUS for Roaming Clients for more information about how to configure DNS to support roaming clients.
Centrally managed WSUS servers utilize replica servers. Replica servers are not administered separately, and are used only to distribute approvals, groups, and updates. The approvals and targeting groups you create on the master server are replicated throughout the entire organization, as shown in the "WSUS Centralized Management (Replica Servers)" illustration below. Remember that computer group membership is not distributed throughout the replica group, only the computer groups themselves. In other words, you always have to load client computers into computer groups.
You should also make sure that the upstream server is configured for all the languages required by its replica servers. If you add languages to the upstream server, you should copy the new updates to its replica servers. Changing language options on the upstream server alone might result in a mismatch between the number of updates that are approved on the central server and the number of updates approved on the replica servers
Distributed management offers you full control over approvals and computer groups for the
WSUS server, as shown in the "WSUS Distributed Management" illustration below. With the
distributed management model, there is usually an administrator at each site who decides which update languages are needed, creates computer groups, assigns computers to groups, tests and approves updates, and ensures that the correct updates are installed on the right computer groups. Distributed management is the default installation option for all WSUS installations.
You can use express installation files to limit the bandwidth consumed on your local network, at the cost of bandwidth consumption on your Internet connection and disk space. By default WSUS does not use express installation files. To understand the tradeoff, you first have to understand how WSUS updates client computers.
Updates typically consist of new versions of files that already exist on the computer being
updated. On a binary level these existing files might not differ very much from updated versions.
The express installation files feature is a way of identifying the exact bytes that change between different versions of files, creating and distributing updates that include just these differences, and then merging the original file with the update on the client computer. Sometimes this is called delta delivery because it downloads only the difference, or delta, between two versions of a file.
When you distribute updates this way, there is an initial investment in bandwidth. Express
installation files are larger than the updates they are meant to distribute. This is because the
express installation file must contain all the possible variations of each file it is meant to update.
The upper part of the "Express Installation Files Feature" illustration shows an update being
distributed with express installation files; the lower part of the illustration shows the same update being distributed without using express installation files. Notice that with express installation files enabled, you incur an initial download three times the size of the update. However, this cost is mitigated by the reduced amount of bandwidth required to update client computers on the corporate network. With express installation files disabled, your initial download of updates is smaller, but the full size of the download must then be distributed to each of the clients on your corporate network.
Express Installation Files Feature
The file sizes in the "Express Installation Files Feature" illustration are for illustrative purposes only. Each update and express installation file varies in size, depending on what files need to be updated. Further, the size of each file actually distributed to clients by using express installation files varies depending upon the state of the computer being updated.
Important
Express installation files are often larger than the updates they are meant to distribute.
On the other hand, it is always less expensive to distribute updates within a network
using express installation files than to distribute full update files.
Not all updates are good candidates for distribution using express installation files. If you select this option, you obtain express installation files for any updates being distributed this way. If you are not storing updates locally, you cannot use the express installation files feature. By default, WSUS does not use express installation files. To enable this option, see Advanced Synchronization Options.
Recommendations for hardening your WSUS server.
Recommendations for adding authentication between chained WSUS servers in an Active
Directory environment.
Recommendations for implementing the Secure Sockets Layer protocol on WSUS.
2. Support about roaming clients to point to nearest wsus server.
3. Manage branch offices
4. Centralized management
6. Distributed management
Branch offices
· Using the BranchCache feature:
BranchCache is a new feature in Windows 7 and Windows Server 2008 R2 that reduces
WAN link utilization and improves application responsiveness. To enable BranchCache
acceleration of content served by the WSUS server, install the BranchCache feature on the
server and the clients, and ensure that the BranchCache service has started. No other steps
are necessary. For information about installing BrancheCache, see the BranchCache Early
Adopter's Guide (http://go.microsoft.com/fwlink/?LinkId=148741).
· Branch offices with low-bandwidth connections:
In some organizations, branch offices have low-bandwidth connections to the central office
but high-bandwidth connections to the Internet. In this case you may want to configure
about how to set up this kind of configuration, see Advanced Synchronization Options.
Support for roaming
clients
If you have many mobile users who log on to your network from different sites, you may want to use the following configuration to allow them to update their computers from the closest WSUS server. In this configuration, shown in the "Roaming Clients Using Different WSUS Servers" illustration below, there is one WSUS server per region, and each region is a DNS subnet. All clients are pointed to the same WSUS server name, which resolves in each subnet to the nearest WSUS server. See Appendix D: Configure WSUS for Roaming Clients for more information about how to configure DNS to support roaming clients.
Centralized management
Centrally managed WSUS servers utilize replica servers. Replica servers are not administered separately, and are used only to distribute approvals, groups, and updates. The approvals and targeting groups you create on the master server are replicated throughout the entire organization, as shown in the "WSUS Centralized Management (Replica Servers)" illustration below. Remember that computer group membership is not distributed throughout the replica group, only the computer groups themselves. In other words, you always have to load client computers into computer groups.
It is possible that not all the sites in
your organization require the same computer groups. The important thing is to create enough computer groups on the administered server
to satisfy the needs of the rest of the organization. Computers at different sites can be
moved into a group appropriate for the site. Meanwhile, computer groups inappropriate for a
particular site simply remain empty. All update approvals, like computer groups, must be created on
the master server.
For step-by-step instructions, see Create
Replica Servers later in this guide.
You should also make sure that the upstream server is configured for all the languages required by its replica servers. If you add languages to the upstream server, you should copy the new updates to its replica servers. Changing language options on the upstream server alone might result in a mismatch between the number of updates that are approved on the central server and the number of updates approved on the replica servers
Distributed management
Distributed management offers you full control over approvals and computer groups for the
WSUS server, as shown in the "WSUS Distributed Management" illustration below. With the
distributed management model, there is usually an administrator at each site who decides which update languages are needed, creates computer groups, assigns computers to groups, tests and approves updates, and ensures that the correct updates are installed on the right computer groups. Distributed management is the default installation option for all WSUS installations.
Using express
installation files
You can use express installation files to limit the bandwidth consumed on your local network, at the cost of bandwidth consumption on your Internet connection and disk space. By default WSUS does not use express installation files. To understand the tradeoff, you first have to understand how WSUS updates client computers.
Updates typically consist of new versions of files that already exist on the computer being
updated. On a binary level these existing files might not differ very much from updated versions.
The express installation files feature is a way of identifying the exact bytes that change between different versions of files, creating and distributing updates that include just these differences, and then merging the original file with the update on the client computer. Sometimes this is called delta delivery because it downloads only the difference, or delta, between two versions of a file.
When you distribute updates this way, there is an initial investment in bandwidth. Express
installation files are larger than the updates they are meant to distribute. This is because the
express installation file must contain all the possible variations of each file it is meant to update.
The upper part of the "Express Installation Files Feature" illustration shows an update being
distributed with express installation files; the lower part of the illustration shows the same update being distributed without using express installation files. Notice that with express installation files enabled, you incur an initial download three times the size of the update. However, this cost is mitigated by the reduced amount of bandwidth required to update client computers on the corporate network. With express installation files disabled, your initial download of updates is smaller, but the full size of the download must then be distributed to each of the clients on your corporate network.
Express Installation Files Feature
The file sizes in the "Express Installation Files Feature" illustration are for illustrative purposes only. Each update and express installation file varies in size, depending on what files need to be updated. Further, the size of each file actually distributed to clients by using express installation files varies depending upon the state of the computer being updated.
Important
Express installation files are often larger than the updates they are meant to distribute.
On the other hand, it is always less expensive to distribute updates within a network
using express installation files than to distribute full update files.
Not all updates are good candidates for distribution using express installation files. If you select this option, you obtain express installation files for any updates being distributed this way. If you are not storing updates locally, you cannot use the express installation files feature. By default, WSUS does not use express installation files. To enable this option, see Advanced Synchronization Options.
Secure WSUS 3.0 SP2 Deployment
This guide includes three ways to enhance the security of your WSUS server:
Recommendations for hardening your WSUS server.
Recommendations for adding authentication between chained WSUS servers in an Active
Directory environment.
Recommendations for implementing the Secure Sockets Layer protocol on WSUS.
==============================================================
Related articles:
WSUS - errors 800B0001 on clients from 2008/2012 server with Wsus role
Wsus - Update to enable WSUS support for Windows 10 feature upgrades KB3095113
Wsus - Windows 10 problem and Update enables ESD decryption provision in WSUS in Windows Server 2012 and Windows Server 2012 R2
Wsus - Choose your best WSUS architecture
2012 R2 - WSUS and reporting Viewer 2008 SP1 that require .NET Framework
WSUS - Install Internet Explorer 11 (IE11) - Windows Server Update Services (WSUS)
WSUS - 3.0 SP2 and Windows 8/2012 Server issue KB2734608
Server - How to set up WSUS on Windows Server 2008 R2
Wsus - Update to enable WSUS support for Windows 10 feature upgrades KB3095113
Wsus - Windows 10 problem and Update enables ESD decryption provision in WSUS in Windows Server 2012 and Windows Server 2012 R2
Wsus - Choose your best WSUS architecture
2012 R2 - WSUS and reporting Viewer 2008 SP1 that require .NET Framework
WSUS - Install Internet Explorer 11 (IE11) - Windows Server Update Services (WSUS)
WSUS - 3.0 SP2 and Windows 8/2012 Server issue KB2734608
Server - How to set up WSUS on Windows Server 2008 R2
Exchange 2007/10 - How export to pst single mailbox or all mailboxes with single command or powershell command
With Exchange 2010 SP1 there is possibility to automatically export single mailbox or all mailboxes and convert them to .pst file (it could be alternative backup procedure)
Here are steps that you need to follow:
1. Give a domain user ability to import Export mailbox with this command
New-ManagementRoleAssignment –Role "Mailbox Import Export" –User "Domain\user_domain"
otherwise:
New-MailboxExportRequest -Mailbox "TEST, user" -FilePath \\SERVERNAME\share_name\TEST.user-export.pst
2. Create a network share and give “Exchange Trusted Subsystem” groups read and write on that share.
3. Create export request like follow:
New-MailboxExportRequest -Mailbox “mailbox_bame” -FilePath “network share”
4. To verify Export request status
Get-MailboxExportRequest | Get-MailboxExportRequestStatistics
Get-MailboxImportRequest
5. To view mailbox export completed and remove them:
Get-MailboxExportRequest | where {$_.status -eq "Completed"}
Remove export mailbox completed:
Get-MailboxExportRequest | where {$_.status -eq "Completed"} | Remove-MailboxExportRequest
Get-MailboxExportRequest | Remove-MailboxExportRequest
6. If you want to backup all mailboexes you can use this script
foreach ($i in (Get-Mailbox | Where {$_.ExchangeVersion.ExchangeBuild.Major -eq 14})) { New-MailboxExportRequest -Mailbox $i -FilePath "\\SERVER_BAME\SHARE\${$i.Alias).pst" }
In case you want to backup only some mailboxes you need to create a .csv file with first row with Alias name followed by Mailboxes alias name or simple mailbox name
foreach ($i in (Import-Csv .\exports.csv)) { New-MailboxExportRequest -Mailbox $i.Alias -FilePath "\\SERVER_BAME\SHARE\$($i.Alias).pst" }
Later you can perform Mass Exports as a scheduled task.
With Exchange 2007 SP3 there is possibility to automatically export single mailbox or all mailboxes and convert them to .pst file but procedure is slightly different than Exchange2010
On Exchange 2007 otherwise you need to perform this task on 32 bit Server with outlook 2003 SP2 using this syntax.
In order to export or import mailboxes to PST files the following requirements must be met:
The user running the task must be an Exchange Organization Admin or an Exchange Server Admin on the server where the mailbox to export/import lives.
[original article]
http://exchangeserverpro.com/export-mailboxes-exchange-server-2010-sp1/
http://www.stevieg.org/2010/07/using-the-exchange-2010-sp1-mailbox-export-features-for-mass-exports-to-pst/
You could be interested to these similar article too:
Exchange 201X- How get all users who have a forwarding email, redirect rule and delegate permission on them mailboxes or Outlook folders
Exchange 2013 - How to monitor it with powershell command
Exchange - Microsoft Exchange Server User Monitor
Exchange 2010 - Poster dell'architettura
Exchange 2010 - How to monitor Exchange Health
Exchange 2010 - How export to pst single mailbox or all mailboxes with single command or powershell command
Exchange 2013 - How to monitor it with powershell command
Exchange 2010 - How to get info on Mobile devices connected via ActiveSync, quarantine any new device and remote Wipe them.
Exchange 2003/2010 - Add a photo to user contact
Here are steps that you need to follow:
1. Give a domain user ability to import Export mailbox with this command
New-ManagementRoleAssignment –Role "Mailbox Import Export" –User "Domain\user_domain"
otherwise:
New-MailboxExportRequest -Mailbox "TEST, user" -FilePath \\SERVERNAME\share_name\TEST.user-export.pst
2. Create a network share and give “Exchange Trusted Subsystem” groups read and write on that share.
3. Create export request like follow:
New-MailboxExportRequest -Mailbox “mailbox_bame” -FilePath “network share”
4. To verify Export request status
Get-MailboxExportRequest | Get-MailboxExportRequestStatistics
Get-MailboxImportRequest
5. To view mailbox export completed and remove them:
Get-MailboxExportRequest | where {$_.status -eq "Completed"}
Remove export mailbox completed:
Get-MailboxExportRequest | where {$_.status -eq "Completed"} | Remove-MailboxExportRequest
Get-MailboxExportRequest | Remove-MailboxExportRequest
6. If you want to backup all mailboexes you can use this script
foreach ($i in (Get-Mailbox | Where {$_.ExchangeVersion.ExchangeBuild.Major -eq 14})) { New-MailboxExportRequest -Mailbox $i -FilePath "\\SERVER_BAME\SHARE\${$i.Alias).pst" }
In case you want to backup only some mailboxes you need to create a .csv file with first row with Alias name followed by Mailboxes alias name or simple mailbox name
foreach ($i in (Import-Csv .\exports.csv)) { New-MailboxExportRequest -Mailbox $i.Alias -FilePath "\\SERVER_BAME\SHARE\$($i.Alias).pst" }
Later you can perform Mass Exports as a scheduled task.
<----------->
<===============================>
With Exchange 2007 SP3 there is possibility to automatically export single mailbox or all mailboxes and convert them to .pst file but procedure is slightly different than Exchange2010
On Exchange 2007 otherwise you need to perform this task on 32 bit Server with outlook 2003 SP2 using this syntax.
In order to export or import mailboxes to PST files the following requirements must be met:
- Export/Import to PST must be run from a 32 bit client machine with Exchange Management Tools installed (Version Exchange 2007 SP1 or later). The 32bit requirement comes from a dependency with the Outlook client.
Microsoft Exchange Server 2007 Management Tools (32-Bit) - Either Outlook 2003 or Outlook 2007 must be installed on the client machine.
The user running the task must be an Exchange Organization Admin or an Exchange Server Admin on the server where the mailbox to export/import lives.
Export-Mailbox -Identity “domain\userdomain” -PSTFolderPath f:\ ArchiviedPST\Archiviedusers.pst
More details here:
https://blogs.technet.microsoft.com/exchange/2007/04/13/how-to-export-and-import-mailboxes-to-pst-files-in-exchange-2007-sp1/
More details here:
https://blogs.technet.microsoft.com/exchange/2007/04/13/how-to-export-and-import-mailboxes-to-pst-files-in-exchange-2007-sp1/
[original article]
http://exchangeserverpro.com/export-mailboxes-exchange-server-2010-sp1/
http://www.stevieg.org/2010/07/using-the-exchange-2010-sp1-mailbox-export-features-for-mass-exports-to-pst/
<-------->
You could be interested to these similar article too:
Exchange 201X- How get all users who have a forwarding email, redirect rule and delegate permission on them mailboxes or Outlook folders
Exchange 2013 - How to monitor it with powershell command
Exchange - Microsoft Exchange Server User Monitor
Exchange 2010 - Poster dell'architettura
Exchange 2010 - How to monitor Exchange Health
Exchange 2010 - How export to pst single mailbox or all mailboxes with single command or powershell command
Exchange 2013 - How to monitor it with powershell command
Exchange 2010 - How to get info on Mobile devices connected via ActiveSync, quarantine any new device and remote Wipe them.
Exchange 2003/2010 - Add a photo to user contact
Server - how to expose QNAP iscsi storage to Vmware based system
During these years I had the opportunity to expose QNAP devices (or other NAS) storage like ISCSI.
For this purpose I indicate this official Veeam tutorial to get this result.
http://files.qnap.com/news/pressresource/product/How_to_set_up_QNAP_NAS_as_a_datastore_via_iSCSI_for_VMware_ESX_4.0_or_above.pdf
The main idea is to expose storage with ISCSI and then connect it to Vmware ESXi.
The best approach it would be to have double switch (for redundancy) and different paths availibility (in this mode) and create a VLAN between ESX(i) and QNAP storage (but it work in any case on same VLAN where there are clients/servers too but with less perfomances)
InfraStructure
QNAP screenshot lun creation
[update 2019.05.13]
Here they are updated links to all QNAP Storage products:
https://www.qnap.com/it-it/product/
For this purpose I indicate this official Veeam tutorial to get this result.
http://files.qnap.com/news/pressresource/product/How_to_set_up_QNAP_NAS_as_a_datastore_via_iSCSI_for_VMware_ESX_4.0_or_above.pdf
The main idea is to expose storage with ISCSI and then connect it to Vmware ESXi.
The best approach it would be to have double switch (for redundancy) and different paths availibility (in this mode) and create a VLAN between ESX(i) and QNAP storage (but it work in any case on same VLAN where there are clients/servers too but with less perfomances)
InfraStructure
QNAP screenshot lun creation
ESXI lun connection
Now Status is enabled
Here they are updated links to all QNAP Storage products:
https://www.qnap.com/it-it/product/
Tips - Rss aggregator/Reader
If you was enthusiastic about Google Reader, that was dismissed some years, ago I will take note, in this post some products that, in my opinion, are quite good (some enhanced feature are not for free):
1. Feedly
2. Old Google Reader
3. Diggy Reader
1. Feedly
2. Old Google Reader
3. Diggy Reader
Software - QTTabBar Explorer addon to have multitab in Windows explorer
QTTabBar ver 1028 (2015-8-11) New
- Extends Explorer by tabs and extra folder views
- Free/Donationware
- Multiple-language support by contributors
- for Windows7 & Windows8 & Windows8.1 & Windows10 (32bit/64bit) + .net Framework 4.0
- Free/Donationware
- Multiple-language support by contributors
- for Windows7 & Windows8 & Windows8.1 & Windows10 (32bit/64bit) + .net Framework 4.0
SCCM 2012 R2 - Cumulative Update 1 for ConfigMgr 2012 SP2 and ConfigMgr 2012 R2 SP1 is available
Full Microsoft Article:
Description of Cumulative Update 1 for System Center 2012 R2 Configuration Manager Service Pack 1 and System Center 2012 Configuration Manager Service Pack 2
here they are error fixed:
otfix Download Available
Description of Cumulative Update 1 for System Center 2012 R2 Configuration Manager Service Pack 1 and System Center 2012 Configuration Manager Service Pack 2
here they are error fixed:
otfix Download Available
Issues that are fixed
Configuration manager client
- 3073015 Registration for an existing client is unsuccessful on System Center 2012 Configuration Manager SP2 and System Center 2012 R2 Configuration Manager SP1
- Computers that are running the Configuration Manager Client evaluate mobile device policies and return states of both "applicable" and "compliant." This issue occurs when a user who is assigned a mobile device management policy logs on to the computer.
Software distribution and content management
- Deleting an application that was previously deployed may cause the SMS Object Replication Manager component to transition to an error state, and errors that resemble the following are logged in the Objreplmgr.log file on the site server:*** [23000][547][Microsoft][SQL Server Native Client 11.0][SQL Server]The DELETE statement conflicted with the REFERENCE constraint "CI_CurrentRuleDetail_CIID_FK". The conflict occurred in database "CM_PRI", table "dbo.CI_CurrentRuleDetail", column 'Setting_CI_ID'.~Failed to delete Deployment Type ScopeId_{GUID}/DeploymentType_{GUID}/1 STATMSG: ID=6004 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OBJECT_REPLICATION_MANAGER" SYS={SiteSErver} SITE=PRI...
Windows 10 - How to install it using the media creation tool
The media creation tool can be used to upgrade your current PC to Windows 10 or to create a USB or DVD and install Windows 10 on a different PC.
Here’s a quick look at the steps to get Windows 10 installed on your PC using this tool.
Download the tool
Find the media creation tool on the Software download page.
There are two versions of the tool, one for a “32-bit operating system” and one for a “64-bit operating system.” To find out which you have, go to Start, type Control panel, select System and security, and then, under System, look at the value for System type:.
If your PC is a 32-bit operating system, on the Software download page, select Download tool now (32-bit version). If your PC is a 64-bit operating system, select Download tool now (64-bit version).
When you're asked, select Run (or choose to Save the tool if you don't want to run it now).
Full Miscrosoft Article
http://go.microsoft.com/fwlink/p/?LinkId=616447
Here’s a quick look at the steps to get Windows 10 installed on your PC using this tool.
Download the tool
Find the media creation tool on the Software download page.
There are two versions of the tool, one for a “32-bit operating system” and one for a “64-bit operating system.” To find out which you have, go to Start, type Control panel, select System and security, and then, under System, look at the value for System type:.
If your PC is a 32-bit operating system, on the Software download page, select Download tool now (32-bit version). If your PC is a 64-bit operating system, select Download tool now (64-bit version).
When you're asked, select Run (or choose to Save the tool if you don't want to run it now).
Full Miscrosoft Article
http://go.microsoft.com/fwlink/p/?LinkId=616447
Subscribe to:
Posts (Atom)