HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

problem with ML 350 G6 Important

 
shehab
Occasional Advisor

problem with ML 350 G6 Important

Hi guys I have a big problem and I hope that you will help me

when I try to use a bootable cd it's name is win mini pe

It's booting but the problem I can't see c: partition Or d: partition


this cd is a virtual windows to use some utilities to fix some problem in windows


I have windows server 2008 standart


plz help


13 REPLIES
Michael A. McKenney
Respected Contributor

Re: problem with ML 350 G6 Important

Use the Windows 2008 DVD and do a repair session instead.
shehab
Occasional Advisor

Re: problem with ML 350 G6 Important

BUT I DID SOME SETTINGS FOR TERMINAL SERVICES

AND PRINTERS FOR MORE THAN 20 CLIENT PC



I'M AFRAID THAT IT WILL BE EREASED
Michael A. McKenney
Respected Contributor

Re: problem with ML 350 G6 Important

You don't do a repair. You get into a repair session and access drive C:.

What did you do before the server crashed? Why do you need access to it? You need to get it fixed first and worry about Terminal services later.
shehab
Occasional Advisor

Re: problem with ML 350 G6 Important

I'LL TELL YOU WHAT IS MY PROBLEM


MY PROBLEM IS I HAVE WINDOWS SERVER 2008 STANDARD COPY


ALL OF MY USERS IN THIS WINDOWS THIER PASSWORDS HAS CHANGED AFTER I DID UPDATES FOR WINDOWS

AND NOW I'M NOT ABLE TO ENTER MY SYSTEM


SO I NEED TO USE WIN MINI PE OR ANY OTHER UTILITY TO CHANGE THE ADMINISTRATOR PASSWORD

SO I'LL BE ABLE TO ENTER MY SYSTEM AND TO PUT PASSWORDS AGAIN

BUT THE PROBLEM WHEN I TRY TO BOOT FROM MY CD


IT'S OK

UNTIL I LOGIN TO VIRTUAL WINDOWS

AFTER THAT I CAN NOT SEE C: OR D: OR EVEN E:


IT JUST MADE VIRTUAL CD IT'S NAME IS B



SO I CANNOT FIND THE OPERATING SYSTEM ROOT



IF YOU HAVE ANOTHER WAY PLZ TELL ME


CUZ ALL OF MY BRANCHES NOW ARE STOPED


AND THEY'RE NOT ABLE TO ENTER DATA



Michael A. McKenney
Respected Contributor

Re: problem with ML 350 G6 Important

You don't need to write in all caps.

I have never seen patches reset passwords. Either two things happened. Virus or Active Directory corruption. Go to the login screen, login as administrator but use the local server name instead of the domain. Don't do a domain login only local.

It could be DNS is not working also. Windows 2003 and 2008 will not access active directory services without DNS.

Try local machine login first.

shehab
Occasional Advisor

Re: problem with ML 350 G6 Important

I DID NOT ENABLE ACTIVE DIRECTORY I JUST WORK WITH WORKGROUP



AND THAT BOOTABLE CD (WIN MINI PE) I USE IT BEFORE ALOT OF TIME AND IT WAS WORKING


IN THIS SERVER IT ALSO WORKING BUT IT CANNOT SEE THE HARD DISK
Michael A. McKenney
Respected Contributor

Re: problem with ML 350 G6 Important

Still try to login without the workgroup name. Just to the server. You can do a repair install and just reset the administrator password. Windows 2008 NTFS is protected. Even if you get into the file system you can't reset the password easily.

Michael A. McKenney
Respected Contributor

Re: problem with ML 350 G6 Important

shehab
Occasional Advisor

Re: problem with ML 350 G6 Important

YOU KHNOW THE PROBLEM NOW IS NOT FROM WINDOWS PROTECTION ITHINK THAT THERE IS A PROTICTION ON THE SERVER FOR THE HARD DISK
shehab
Occasional Advisor

Re: problem with ML 350 G6 Important

DO YOU HAVE ANY IDEA
shehab
Occasional Advisor

Re: problem with ML 350 G6 Important

PLZ HELP
Michael A. McKenney
Respected Contributor

Re: problem with ML 350 G6 Important

What exactly did you do before this problem occured. Give alot of details. Don't type in all caps. Its very annoying reading all caps.
Michael A. McKenney
Respected Contributor

Re: problem with ML 350 G6 Important

Why not do a Windows 2008 active directory server? Maybe the issue is workgroup rights. Users don't have rights to login to the workgroup with terminal services installed.