Later you can use this guide at step 3 with very detailed information
Tips - How to remove DNS unlocker
If you need to remove DNS unlocker you need to download Antimalware bytes
Security - True last logon to monitor AD
Do you need to find the true last logon time for users and computer accounts? Do you need to receive a report of users who haven’t logged on in the last 30 days? Do you need to automatically disable accounts that haven’t logged on in 60 days?
With True Last Logon you can clean up your Active Directory by easily identifying unused or obsolete user and computer accounts based on their true last logon time and account status. You can use the built-in scheduler to run scheduled reports, perform actions such as disabling accounts, removing the user from sensitive groups etc.
True Last Logon handles the complex task of identifying the true last logon time of any Active Directory account (user or computer) by querying all the relevant Active Directory Domain Controllers. It displays this along with detailed account information, enabling you to apply filters and perform bulk actions on the results.
True Last Logon makes it easy to identify accounts in need of attention, e.g. disabled, locked, never logged on, or with a non-expiring password, and then to deal with them in bulk.
- Accurate True Last Logon Time
- Detailed account status
- Automate reports and bulk changes
- Built-in scheduler
- Powerful bulk administration tools
- Move, Delete or Disable redundant accounts
- Command line operation
- Email, print or export reports
- No server components or agents to install
- No changes to Active Directory required
True Last Logon displays the following Active Directory information:
- Users real name and logon name
- Last Logon Date & Time
- Last Logon Timestamp (Replicated value)
- Account Expiry Date & Time
- Enabled or Disabled Account
- Locked Accounts
- Password Expires
- Password Last Set Date & Time
- Logon Count
- Bad Password Count
- Expiry Date
- You can also query for any other attribute (Example: Description, telephone Number, custom attibutes etc)
- http://www.dovestones.com/active-directory-last-logon-tool/
Microsoft - ie 11 last browser supported after 16th january 2016 on win7/8/10
From article:
Beginning January 12, 2016, only the most current version of Internet Explorer available for a supported operating system will receive technical support and security updates, as shown in the table below:
| Windows Desktop Operating Systems | Internet Explorer Version |
| Windows Vista SP2 | Internet Explorer 9 |
| Windows 7 SP1 | Internet Explorer 11 |
| Windows 8.1 Update | Internet Explorer 11 |
| Windows Server Operating Systems | Internet Explorer Version |
| Windows Server 2008 SP2 | Internet Explorer 9 |
| Windows Server 2008 IA64 (Itanium) | Internet Explorer 9 |
| Windows Server 2008 R2 SP1 | Internet Explorer 11 |
| Windows Server 2008 R2 IA64 (Itanium) | Internet Explorer 11 |
| Windows Server 2012 | Internet Explorer 10 |
| Windows Server 2012 R2 | Internet Explorer 11 |
| Windows Embedded Operating Systems | Internet Explorer Version |
| Windows Embedded for Point of Service (WEPOS) | Internet Explorer 7 |
| Windows Embedded Standard 2009 (WES09) | Internet Explorer 8 |
| Windows Embedded POSReady 2009 | Internet Explorer 8 |
| Windows Embedded Standard 7 | Internet Explorer 11 |
| Windows Embedded POSReady 7 | Internet Explorer 11 |
| Windows Thin PC | Internet Explorer 8 |
| Windows Embedded 8 Standard | Internet Explorer 10 |
| Windows 8.1 Industry Update | Internet Explorer 11 |
For customers running on an older version of Internet Explorer, such as Internet Explorer 8 on Windows 7 Service Pack 1 (SP1), Microsoft recommends customers plan to migrate to one of the above supported operating systems and browser combinations by January 12, 2016.
Extra It - trust relationship basis
Here is interesting article that indicate relationship basis that are useful on work and in private life too :
Walk Your Talk. Mean what you say and keep your word. Deliver your committed tasks and duties on time and in full. Be consistent and reliable. Arrive promptly to meetings. If you might risk missing an agreed timeline, proactively communicate and explain it, apologize and come forward with a new proposal. Try not missing it a second time to protect your reputation. Lead by example and permanently demonstrate that you deliver on your promises and that others can count on you.
Communicate Frequently And Openly. Direct, quick, accurate, and honest communication builds trust. Share regularly with others. This underlines that you have no hidden agenda. Address possible trust issues within a team in an open and prompt manner. In this context also crucial to develop and possess good active listening skills.
Tell The Truth And Take A Stand. Be honest and don´t lie. This is not as easy as it might sound. Of course, we wouldn´t admit it, would we? Anyway, it´s key not leaving out relevant facts, figures, and opinions when discussing and arguing. Even, and especially, when it´s awkward and painful. People will appreciate it. Also be willing to say no. You can´t be everything to everyone. Taking a stand based on sound arguments - well and politely articulated - will earn you respect and trust.
Be Transparent And Unite. Share your objectives, strategy, agenda, and values. People want to know what you think and believe and to understand how they might fit into the picture. This gives them security and confidence in you and your intentions. Create a common identity and establish a sense of companionship.
Show People That You Care About Them. Be out for others and not primarily for yourself. Appreciate all people you´re dealing with. Show sensitivity to their interests, wishes, and needs. Value them and thank them. Express sincere gratitude rather two times too often than missing it just once. Do it from the heart.
Empower Others. Show people that you trust them. Grant flexibility, stimulate initiative- taking, and ask for regular feedback. Have faith in others skills and capabilities. Be willing to let go and to share power. "The best way to find out if you can trust somebody is to trust them" (E. Hemingway).
Focus On The Positives. Don´t punish mistakes. As they can happen think and speak about them in a results-oriented and forward-looking way. Jointly look with others for solutions and implement actions to avoid that they´ll happen again.
Coach And Train Others. Guide people around you and assist them in finding their way and the right solutions for themselves. Don´t tell them what to do. Instead ask them for their opinions. Support them in becoming great and outstanding.
Follow High Ethical Standards. Do the right things. Even, and especially, when it might be hard. People will like, respect, and trust your integrity.
Admit Mistakes And Weaknesses. Fortunately, you´re only human. So, when you don’t do the right thing, admit it. Be transparent, authentic and willing to talk about your mistakes and faults in a constructive manner. When you are vulnerable and have nothing to hide you radiate trust. That´s what people love.
Establish Long Term Relationships. Trust is usually not the result of short term actions and profits. It´s stemming from deeper values, ethics, and fundamental principles. Take your time and don´t rush. Be willing to let trust evolve and flourish. The best trust fertilizer is to "give without any strings attached.“ Don´t expect always something in return.
https://www.linkedin.com/pulse/20140330130915-175081329-how-to-become-a-leader-of-trust?_mSplash=1&trk=nus-cha-roll-art-title
....
Walk Your Talk. Mean what you say and keep your word. Deliver your committed tasks and duties on time and in full. Be consistent and reliable. Arrive promptly to meetings. If you might risk missing an agreed timeline, proactively communicate and explain it, apologize and come forward with a new proposal. Try not missing it a second time to protect your reputation. Lead by example and permanently demonstrate that you deliver on your promises and that others can count on you.
Communicate Frequently And Openly. Direct, quick, accurate, and honest communication builds trust. Share regularly with others. This underlines that you have no hidden agenda. Address possible trust issues within a team in an open and prompt manner. In this context also crucial to develop and possess good active listening skills.
Tell The Truth And Take A Stand. Be honest and don´t lie. This is not as easy as it might sound. Of course, we wouldn´t admit it, would we? Anyway, it´s key not leaving out relevant facts, figures, and opinions when discussing and arguing. Even, and especially, when it´s awkward and painful. People will appreciate it. Also be willing to say no. You can´t be everything to everyone. Taking a stand based on sound arguments - well and politely articulated - will earn you respect and trust.
Be Transparent And Unite. Share your objectives, strategy, agenda, and values. People want to know what you think and believe and to understand how they might fit into the picture. This gives them security and confidence in you and your intentions. Create a common identity and establish a sense of companionship.
Show People That You Care About Them. Be out for others and not primarily for yourself. Appreciate all people you´re dealing with. Show sensitivity to their interests, wishes, and needs. Value them and thank them. Express sincere gratitude rather two times too often than missing it just once. Do it from the heart.
Empower Others. Show people that you trust them. Grant flexibility, stimulate initiative- taking, and ask for regular feedback. Have faith in others skills and capabilities. Be willing to let go and to share power. "The best way to find out if you can trust somebody is to trust them" (E. Hemingway).
Focus On The Positives. Don´t punish mistakes. As they can happen think and speak about them in a results-oriented and forward-looking way. Jointly look with others for solutions and implement actions to avoid that they´ll happen again.
Coach And Train Others. Guide people around you and assist them in finding their way and the right solutions for themselves. Don´t tell them what to do. Instead ask them for their opinions. Support them in becoming great and outstanding.
Follow High Ethical Standards. Do the right things. Even, and especially, when it might be hard. People will like, respect, and trust your integrity.
Admit Mistakes And Weaknesses. Fortunately, you´re only human. So, when you don’t do the right thing, admit it. Be transparent, authentic and willing to talk about your mistakes and faults in a constructive manner. When you are vulnerable and have nothing to hide you radiate trust. That´s what people love.
Establish Long Term Relationships. Trust is usually not the result of short term actions and profits. It´s stemming from deeper values, ethics, and fundamental principles. Take your time and don´t rush. Be willing to let trust evolve and flourish. The best trust fertilizer is to "give without any strings attached.“ Don´t expect always something in return.
https://www.linkedin.com/pulse/20140330130915-175081329-how-to-become-a-leader-of-trust?_mSplash=1&trk=nus-cha-roll-art-title
Tips - How to solve Windows Phone software uninstallation error
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
{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
Subscribe to:
Posts (Atom)