NetApp (DISK BAD LABEL) ERROR

Posted: April 25, 2018 in NetApp

I’m checking my servers and storage and I notice an amber led on one of my NetApp storages, a defective HDD. I replace the disk I get the green light again from the Storage; All is Good. a couple of minutes later I received and E-mail from my NetApp Storage:

netapp04@itnetmasters.com : HA Group Notification from NetApp04 (DISK BAD LABEL) ERROR.

1. So I used Putty to login to the storage and I executed command: vol status -r

NetApp_Bad_Label_volstatus-r

and under Broken Disk I found the disk (which is the one I recently added).

2. Executed command: priv set advanced

NetApp_Bad_Label_privsetadvanced

3. Executed command: disk unfail -s 0C.00.10 (which is unfail disk with the bad label and 0C.00.10 is the device name)

NetApp_Bad_Label_diskunfail-s

4. Now that the disk is unfailed execute command: vol status -s

NetApp_Bad_Label_volstatus-s_2

5. After executing vol status -s at the end of the output it indicated disk has not being zeroed. Execute command: disk zero spares

NetApp_Bad_Label_diskzerospares

6. Now you can execute command: vol status -s to check how the zeroing process.

NetApp_Bad_Label_volstatus-s_3

afterward you can exit. And you are Done! I found this information on the NetApp Community web page. Enjoy

 

 

Advertisements

Yesterday I get a call from a user that he is unable to access the Internet and receives a “Proxy not Responding” error. I check the proxy server and see no errors in the Event Viewer. I open the Proxy Application and no errors, I check the services and notice that the little icon with that indicates that the server in online is red instead of green. I check windows services and the application has not started. I start the service, it fails; time to check deeper, SQL Server services are online I proceed to check the SQL Server Configuration Manager and WHAM!:

SQL-Server-Configuration-manager-Invalid-class-0x80041010

Cannot connect to WMI provider. You don not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 and later servers with SQL Server Configuration Manager. Invalid class [0x80041010]

I had dealt with this issue before but I forgot to document it, so I visited Microsoft | Developer Blog

Worked like a charm, Proxy server is operational, User is happy and so am I.

Don’t forget to leave a reply!

Merry Christmas 2017!

I was checking the logs on my Exchange Server and noticed Event 2937, MSExchange ADAccess. I had this warning for quite some time now and ignored it, with a little time on my hands I decided to fix it once and for all.

Event 2937-MSExchange-ADAccess.PNG

So the run down is that there is a value on the account that is pointing to a deleted object in Active Directory.

I connected to my DC, you can also use any computer connected to the domain that has RSAT (Remote Server Administration Tools) installed:

1. Open ADSIEdit

ADSIEdit

2.  Select “Default naming context” under Select a well known Naming Context

Connection-Settings

 

3.  Search for the location of the user (in my case)

CN=Administrator ,OU=OPS ,OU=MIS ,DC=itnetmasters ,DC=com

properties

4.  One located the object I searched for a property known as “homeMDB”  which contains the DB where the mailbox for the users resides.

CN=MIS,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=itnetmasters,DC=com

5. Now the value that is taunting us is “msExchPreviousHomeMDB” which in my case contained value:

CN=ITNETMASTERS-MIS\0ADEL:87ff5506-9117-44a1-b284-8e99c0170d68,CN=Deleted Objects,CN=Configuration,DC=itnetmasters,DC=com

6. Clear the value of “msExchPreviousHomeMDB”

7. Click Apply

8. Click OK

9. Close ADSIEdit

Issue has been resolved, the warning is gone.

*This fix relates to and User object if it is another type of AD object you need to connect to “Configuration” in ADSIEdit and perform the appropriate configuration changes.

I recently has an issue with My Lync Server 2010, after the CA certificate expired, long story short, I had to renew the Lync server 2010 Certificate that ensures secure transport.

Event61002.PNG

To fix the issue go to: Microsoft TechNet-Renewing Lync Server 2010, 2013 Certificates, now before you start Remember to:

  1. Open the Lync Server 2010 – Deployment Wizard (in my case)LyncServer2010DeploymentWizard
  2. Install or Update Lync Server SystemInstall-Update-Lync-Server-System
  3. Select Step 3: Request, Install or Assign CertificatesStep3

after this follow the TechNet instructions once you are done remember to execute Step4 ” Start Services” step4.png now you are good to go services are up and running and the error is gone.

🙂 Enjoy

I’m working with a customer that has issues with their application and I had to check SQL Server Configuration. I connected to the SQL Server Configuration Manager and received the following error:

Error message when you open SQL Server Configuration Manager in SQL Server: “Cannot connect to WMI provider. You do not have permission or the server is unreachable”

SQL-SERVER-error

I checked Microsoft Support web page, after implementation the SQL Server Configuration Manager was operational and Issue was corrected.

SQL-Configuration-Manager-Operational

Special thanks to Microsoft Support Team!

Enjoy! 🙂

 

Event 36870, Schannel: A fatal error occurred when attempting to access the SSL server credential private key. The error code returned from cryptographic module is 0x8009030D. The internal error state is 10001.

Event_36870_Schannel

A solution was found on Ask the Performance Team Blog I applied the solution, tried to Remote Desktop Connection to the Server and a pop-up with error:

An Authentication error has occurred. The Local Security Authority cannot be contacted…

RDC-error

… I forgot the cardinal rule:

After making permission changes, Reboot.

After a restart of the server, Remote Desktop Connection was successful.

A special thanks to the “Ask the Performance Team Blog“.

Enjoy. 🙂

SMTP Relay for Office 365

Posted: October 20, 2017 in Office365

I recently had a customer that needed to send scanned documents from a multifunctional printer to Office365:

  • Check to see if the Printer supports TLS (needed to send to Office 365)

In this case the printer did not, so I had to go to plan B:

  1. Create SMTP Server
  2. Configure Office 365 Connector

 I.  Create SMTP Server

In this scenario I used Windows Server 2012 R2 in a Hyper-V Environment.4-Hyper-V-Server

A. SMTP Feature

  • Open the Add Roles and Features Wizard

5 - Add-Roles-Features

  • Click Next

6-Role-based-or-feature-based-install

  • Click Next

7-Select-Destination-Server

  • Click Next

8-Server-Roles

  • Select SMTP Server on Features

9-Features

  • Click on “Add Features”

10-SMTP-Feature

  • click Next

11-SMTP-Feature

  • Click Next

12-Web-Server-Role-IIS

  • Click Next

13-Role-Services

  • Click Install

14-Confirmation

  • When Installation finishes click “Close”

15-Results

B. Configure SMTP Server

  • Open IIS 6.0 Console

16-IIS-6-0-Console

  • Expand SMTP (Local Computer)

17-SMTP-Server

  • On SMTP Virtual Server Properties go to Access Tab

19-SMTP-Properties-Access

  • On Access Tab open “Authentication”
  • Anonymous access must be checked
  • Click OK

20-SMTP-Access-Authentication

  • On Access Tab open “Relay”
  • Add the devices IP that will use this server as SMTP Relay.
  • Click OK

21-SMTP-Access-Relay

  • Open Delivery Tab

21-SMTP-Delivery

  • On Delivery Tab, Open Security and select “Basic Authentication”
  • input the information of the Service Account created for this task.
  • “TLS encryption” (without TLS Office 365 will deny the relay)
  • Click OK

21-SMTP-Delivery-OutBound-Security

  • Open Outbound Connections
  • Change the TCP Port to: 587 (default Office 365 port)
  • Click OK

22-SMTP-Delivery-OutBound-Connections

  • Open Advanced Delivery
  • Input the “Fully-qualified domain name” for the Server
  • Input the Office365 Smart host: SMTP.OFFICE365.COM
  • Click OK

23-SMTP-Delivery-Advanced-Delivery

  • Return to the SMTP Virtual Server Properties Access Tab
  • TLS requires a certificate.

22-SMTP-Properties-Access-SecureComm

C.  Configure Secure Communication (TLS)

  • Open IIS 7.0 Console

23-IIS-7-0-Console

  • Click on the SMTP Server
  • Select Server Certificates

24-IIS-7-0-Console

  • Select Create Self-Signed Certificate

25-IIS-Manager-Server-Certificates

  • Specify the friendly name for the certificate
  • Personal must be selected for the Certificate Store

26-IIS-Manager-CreateSelfSignedCert

  • Close the IIS 7.0 Manager Console

27-IISManager_ServerCertificates-WebHosting

  • Go back to IIS 6.0 Manager Console
  • Open the SMTP Virtual Server Properties
  • Select the Access tab “A TLS certificate is found with expiration date…”
  • TLS is now enabled and ready to be used.

27-IISManager-TLS-Available

D.  Test SMTP Server

  • To test SMTP server i will use putty to connect to smtp server
  • remember when using telnet SMTP requires port 25

28-SMTP-Server-TEST-1

>helo

>MAIL FROM:  %address of Service Account that will send the E-mails%

>RCPT TO: %E-mail address of the account that will receive the test message%

>Data %Information that will be sent on the test message%

> . %To End and send the message%

29-SMTP-SERVER-TEST-2

E.  Configure SMTP Service to Automatically start

  • Open Services Management Console
  • Search for: Simple mail Transfer Protocol

30-SMTP-Service

  • Open the SMTP Properties
  • Change Startup type to Automatic
  • Click OK

31-SMTP-SERVICE-AUTO

II.  Configure Office 365 Connector

  • Login to Office 365 and Select the Admin icon

1-Office365Console

  • Select Exchange on the Office 365 Admin Center

2-Office365AdminCenter

  • Create Connector

3-Office365ExchangeAdminCenter-Connectors

 

Wait and hour and the test email should arrive at it’s destination and you are ready to Go.

ENJOY 🙂