My computer cannot recognize my Toshiba 1TB external hard drive

Today i faced a new issue.
issue was
"My computer cannot recognize my Toshiba 1TB external hard drive"
i tried on both Windows 7 and 8.1, but no luck.
while connecting the drive system was detecting to it. a pop up appeared that a new device installed successfully.
also shown in device manager.
but not showing in my computer. i was unable to access.

solution was.
actually the drive was password protected by Toshiba password tool.
after downloading/installing this tool from Toshiba official website.
the system restart and after restart and login to the system the Toshiba password tool asking for password.
then after entering the password.
It was accessible.
 

Services are in starting state in Exchange 2013 Mailbox and CAS role ECP and OWA are not accessible

Today i start to make ready a DR of exchange 2013, the installation of exchange Mailbox and CAS role was already done and after that the server was power off for couple of weeks.
after starting the server i found that the /ECP and OWA were not accessible and  services were in starting state and the exchange management shell was also not connecting to itself and was trying to connect the PR Mailbox CAS servers and giving this error.

"VERBOSE: Connecting to MBXCAS.domain.com
 New-PSSession : [MBXCAS.domain.com] Processing data from remote server MBXCAS.domain.com failed
 with the following error message: The WinRM Shell client cannot process the request. The shell handle passed to the WSMan Shell function is not valid. The shell handle is valid only when WSManCreateShell function completes successfully. Change the request including a valid shell handle and try again. For more information, see the about_Remote_Troubleshooting Help topic.
 At line:1 char:1
 + New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha" 

In event viewer Application logs the following events were there.
Event ID 4027"
Process MSExchangeHMWorker.exe (ExHMWorker) (PID=8440). WCF request (Get Servers for Domain.com) to the Microsoft Exchange Active Directory Topology service on server (TopologyClientTcpEndpoint (localhost)) failed. Make sure that the service is running. In addition, make sure that the network ports that are used by Microsoft Exchange Active Directory Topology service are not blocked by a firewall. The WCF call was retried 3 time(s). Error Details

No Suitable Directory Servers Found in Forest Domain.com Site SiteName and connected Sites"

Event ID 2112

"
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=4400). The Exchange computer DC1.Domain.com does not have Audit Security Privilege on the domain controller DC1.Domain.com. This domain controller will not be used by Exchange Active Directory Provider.
Event ID 2142

"
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=4400) Forest domain.com Topology discovery failed, error details

No Suitable Directory Servers Found in Forest Domain.com Site SiteName and connected Sites.. "

after digging into it i came to know that this server computer object was not added in EXCHANGE SERVER group in active directory after adding into this group i restart the server and after restart everything was working fine. Exchange management shell start normally, all services was running normally.

But /ECP and OWA was not accessible.
i open IIS and go to SITE and right click Exchange Back End select Binding and select https and click on edit button and in SSL certificate Select "Microsoft Exchange" certificate but when click on View to check its property then on Certification path Tab this certificate status was inactive.
for this i went to local certificate store in Certificate MMC and went to this server local certificate store and check property "Servername.domain.com" on general tab its name was "Microsoft Exchange" in certificate Purposes i select option "Enable all porpose of this certificate" and click ok.
after this restart IIS and then  /ECP and OWA were also accessible.

 

The target principal name is incorrect DC not replicating in AD 2008

Today i Start two DCs in a site which were down from couple of weeks and after checking their health found that both DCs have replication issues with DCs in other sites.

Now my steps to resolve this issue were as bellow.

(1) First i check network configuration and also check the required ports to be opened and Found OK
(2) Then i compare time of faulty DCs with PDC and found OK
(3) Then i went to AD sites and services and tried from there replication but got the following error.
"The following error occurred during the attempt to synchronize naming context CN=Configuration, DC=abc, DC=com from domain controller dc1 to domain controller dc2:
the target principal name is incorrect"
(4) Then i went to commandprompt and tried "Repadmin/showrepl and Repadmin/syncall etc"
but got the following error
"AD Replication error -2146893022: The target principal name is incorrect"

(5) I use the procedure in (http://nawazblogger.blogspot.com/2013/09/the-trust-relationship-between-this.html) and now came to know that I have to reset the password of both faulty DCs as in ADSI
edit of faulty DC and functional DCs it was different in pwdlastset in faulty and functional DCs .
To resolve this issue i went AD users and computer and then DCs OU and try right click on both DCs and select reset but got the following error.

"Server "DC1" is a domain controller you cannot reset the password of this object"

(6) Then i try the following command to reset but before this went to Services on this DC and stop the KDC service and set the startup type to manual and restart the server and after completion of this command restart this service as was before.
netdom resetpwd /s:DomainControler /ud:domain\user1 /pd:*
it asked for password and after typing the password and hitting enter key i got the bellow error while using DomainController of other site.
"The machine account password for the local machine could not be reset.
The network path was not found.
The command failed to complete successfully."
Then i went
Then i try to use "DomainController" as its own name as this server is domain controller and command was successful got this message.
The machine account password for the local machine has been successfully reset.
 The command completed successfully
(7) Then i check from ADSIEDIT of faulty and functional DCs and found that pwdlastset date was same.
(8) Now went to AD site and Services and also from command prompt with "Repadmin /showrepl and Repadmin /syncall etc"

and every thing was OK. all errors gone

Can not Print or Save Microsoft Baseline Security Analyzer report

"print this report" not working in Baseline Security Analyzer explorer

today i ran MBSA to scan a system and after completion of scan i want to print the report.
But "print this report" was not work.

solution:

go to control panel and then open Devices and printers and select the "Microsoft XPS document writers" as no hardware printer was not installed on this system.
after this i was able to print the report/Save the report in *.xps format.

 

Changes to the public group membership cannot be saved. you do not have sufficient permission to perform this operation on this object (Resolved)

After migrating from Microsoft exchange 2007 to Microsoft exchange 2013 outlook users were unable to Modify members of distribution groups in outlook.

Getting error while updating groups in outlook:

Changes to the public group membership cannot be saved. you do not have sufficient permission to perform this operation on this object
Open your exchange control panel (https://url/ecp) and then go to permissions--> user roles-->double click on Default role assignment policy and then go to "MyDistributionGroups" and check and save

The job failed with the following error: A failure occurred querying the Writer status. Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Failed during prepare snapshot operation (8).

Error:
The job failed with the following error: A failure occurred querying the Writer status.  Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Failed during prepare snapshot operation (8).

Solution:

First check the VSS provider/writer status that are running on your server.

1. Click Start > Run and type CMD, and then click OK.
2. type vssadmin list providers, then press ENTER.
3. it will show the VSS providers. like Microsoft exchange writer, wmi writer etc.

Now run the following command to show their status.

4. Type vssadmin list writers, and then press ENTER.
5. Confirm that all the VSS writers are showing:

• State: [1] Stable
• No error

if any Writer is not normal/stable state, restart the server. after restart all writers should be stable.
then run the backup, it should be ok.

you didn't get signed in. It might be your sign-in adress or logon credentials. so try those again. if that doesn't work, contact your support team

Few days ago I came across an issue in my organization that some lync clients were unable to login. their client prompting for credentials again and again.  I have Lync Server 2010 environment.
If any user Lync client prompting for password and not connecting then first

(1)                Check network connectivity.


If the network connectivity is fine then go to  the following locations, delete the “Communicator” folder and restart the system.


(1)    "C:\Users\user\AppData\Local\Microsoft"

(2)    "C:\Users\user\AppData\Roaming\Microsoft"

(3)    “C:\Users\user\AppData\LocalLow\Temp\Microsoft”
If still the issue not resolved then make sure that the above "communicator" folders or delete and reinstall the lync client on their system.


for further investigation go to cmd and check that from where this client system is authentiacted. go to that DC and check this user lastlogon time, through "net user userid"
also check client and dc time due to time may also this issue occure.

How to apply screen saver through group policy in Active directory 2008 R2 Domain

Applying screen saver is an easy task you only have to apply the following steps.

Please be care full that your screen saver file is not a big one as it may chock your network if it have a big size and users system start to download at the same time.

(1) You have to create your screen saver *.scr file (DomainScreensaver.scr). you need tool to create .scr file.

now place this "DomainScreensaver.scr"  in a folder like "\\servername\foldername" share it. on sharing tab add everyone and give read permission.

on security tab add everyone and give (read and execute, list folder contents, read) permissions.

 

(2) You also have to create your logon script so while a user logging to his/her system the screen saver file (DomainScreensaver.scr) will be downloaded to user system. For which you have to create the .bat file

How? (open notepad file and type

 

md "C:\ScreenSaver"

xcopy \\servername\foldername\DomainScreensaver.scr C:\ScreenSaver

 and save this file as Screensaverphoto.bat

It will download the content(DomainScreen saver.scr) from share location i.e \\servername\foldername to user’s system C:\screensaver.

 (3) share the folder (\\servername\foldername) which contain the screen saver(Screensaverphoto.bat) and give read rights to everyone on this folder.

 

Now you are going to create/configure GPO, So follow these steps

(1) Start à Group Policy Management.

(2) Create a group policy “SS Client”.

(3) Right click on it and select Edit.

(4) Go to user configuration windows settings à Scripts (Logon/logoff)

(5) Double click on logon à show files—go to screensaverphoto.bat file location.

New kept this location/folder ( \\domain.com\sysVol\domain.com\{FD692A-----}\User\Scripts\Logon )   open.

(6)

Go to the location where you have created “screensaverphoto.bat” file and right click on this file and select copy. now close this folder and go above location (mentioned in step 5) and past it there (\\domain.com\sysVol\domain.com\{FD692A-----}\User\Scripts\Logon )

(7) Now go to Logon properties window and click on Add button

And select the “Screensaverphoto.bat” file.

And click OK.

(8) Now go to User configuration à Administrative templates

Control panel à Personalization

(a) Click on Enable Screen Saver and select Enabled.

 

(b) Click on Password protect the screen saver and select Enabled.

(c) Click on Screen saver timeout select Enabled and mention time like seconds 90 etc.

(d) Click Force Specific screen saver C:\screensaver\DomainScreensaver.scr (it will copy screensaver on this location on client system)

Now your GPO is ready, so you need to apply it.
Go to the desired OU in Group policy management and right on that OU.
select link an existing GPO and select "SS Client" GPO and click OK.
you can also enforce etc.

And that's it. Done

Troubleshooting.
you can check on any client screen saver is not applying.
(1) you can use GPresult /r to check that the GPO is applied or not
(2) you can use rsop.msc to check that which settings are applied on your client system.
(3) to check that the screen saver file is downloaded to client system or not go to location (C:\screensaver) that screen saver file is downloaded or not.
(4) you can run the command (xcopy \\servername\foldername\ C:\ScreenSaver) that it is working fine or not.
(5) Command GPresult with different switches will also help to troubleshoot
(6) if you have accessed a system with RDP, then you may be unable to see the Screen saver. So will be better to check on a system on which you have logged in locally.