Issues with Broadcom NetXtreme II series NIC Card/Driver - Page 2

jdean · 01-02-2008, 03:39 PM

Try this one. The [SysprepMassStorage] has to be present at the end despite it being an empty entry.

[Display]
BitsPerPel = 32
Vrefresh = 60
Xresolution = 1024
Yresolution = 768
[Unattended]
OemSkipEula=Yes
InstallFilesPath=C:\sysprep\i386
[GuiUnattended]
AdminPassword=*
EncryptedAdminPassword=NO
OEMSkipRegional=1
TimeZone=20
OemSkipWelcome=1
[UserData]
ProductKey=key
FullName=name
OrgName=org
ComputerName=%NAME%
[SetupMgr]
DistFolder=C:\sysprep\i386
DistShare=windist
[Identification]
JoinDomain=our domain
DomainAdmin=domain\admin
DomainAdminPassword=password
[Networking]
InstallDefaultComponents=Yes
[Sysprep]
BuildMassStorageSection=Yes
[SysprepMassStorage]

Quote:

Originally Posted by jdean

I haven't forgotten about you cletus. I just started at a new job and I don't have test boxes which is why it is taking me so long to get you an answer.

cl3tUs · 01-03-2008, 09:43 AM

Congrats!!!! I hope you enjoy it. I'm just trying to work through that Sysprep not running fully.

cl3tUs · 01-03-2008, 11:20 AM

I added that and it took about 30 secs. I'm trying to locate an Intel box to see if that is the problem.

cl3tUs · 01-11-2008, 01:43 PM

I've located a HP D530 SFF machine that had an Intel card. Here's the dilemma. It has a Broadcom NIC on the motherboard. It also has an Intel NIC card that is in the PCI slot.

I disabled the Broadcom NIC card in BIOS and set the Intel card to boot first. It loads doesn't prompt me to push F8, which I assume is good. It goes right into trying to script the OS, but when it tries to go into WinPE, I see the "Loading Ramdisk image" part and then it says "Please Wait" and never moves beyond that screen.

Did you know that "stewardesses" is the longest word that is typed with just your left hand?

cl3tUs · 01-17-2008, 02:28 PM

N/M on that one. That was because I didn't have enough RAM to get in WinPE. I did that and am functioning now, up to the part where I do Sysprep. I'm telling the job to capture the image and to "Enable mass storage device support using built-in drivers.

The sysprep process still runs in about 30 seconds...

Any other ideas? I'm all out.

cl3tUs · 01-17-2008, 04:21 PM

Tried again and due to it not building mass storage, I lost a lot of hardware. Strange.

jdean · 01-17-2008, 05:56 PM

Are you choosing the fully automated install option in setup manager or the semi-automated?

Quote:

Originally Posted by cl3tUs

Tried again and due to it not building mass storage, I lost a lot of hardware. Strange.

cl3tUs · 01-18-2008, 10:37 AM

Not to sound like a noob, but where would I check that?

jdean · 01-18-2008, 07:14 PM

When you use Setup Manager to create the sysprep.inf file, it will ask you if this is going to be a fully automated sysprep or a semi-automated sysprep.

You should choose fully automated, enter in EVERYTHING it asks, verify it works and then you can remove components of the INF you do not want.

Quote:

Originally Posted by cl3tUs

Not to sound like a noob, but where would I check that?

cl3tUs · 01-22-2008, 10:51 AM

I do not remember making the sysprep. It's been so long. I'm going to make a new one and try that out.

cl3tUs · 01-22-2008, 11:34 AM

The thing we have in our computer name is %NAME%. I remember trying to put that in the sysprep build during this process and it wouldn't let me. What should I put there so that the name generated will reflect what is in the DS?

cl3tUs · 01-22-2008, 11:37 AM

Here's what that generated for me. Notice it didn't do the Sysprep Mass Storage.

;SetupMgrTag
[Unattended]
OemSkipEula=Yes
InstallFilesPath=C:\sysprep\i386

[GuiUnattended]
AdminPassword=*
EncryptedAdminPassword=NO
OEMSkipRegional=1
TimeZone=20
OemSkipWelcome=1

[UserData]
ProductKey=secret secret, he's got a secret
FullName="The Chickasaw Nation"
OrgName="The Chickasaw Nation"
ComputerName=%NAME%

[TapiLocation]
CountryCode=1

[SetupMgr]
DistFolder=C:\sysprep\i386
DistShare=windist

[Identification]
JoinDomain=with parts made
DomainAdmin=IN
DomainAdminPassword=Japan

[Networking]
InstallDefaultComponents=Yes

Even then, Sysprep is still running in around 30 secs.

jdean · 01-22-2008, 12:06 PM

Do the full Setup Manager automated setup and put static values into the fields. Right now you are trying to get sysprep to work and shouldn't worry about the DS interaction.

you need sysprep just to work properly before you move on to the next step with the DS.

Quote:

Originally Posted by cl3tUs

The thing we have in our computer name is %NAME%. I remember trying to put that in the sysprep build during this process and it wouldn't let me. What should I put there so that the name generated will reflect what is in the DS?

cl3tUs · 01-22-2008, 12:08 PM

Sounds good. So I'm going to send my presysprep job to the one I've been working with and manually sysprep it and see what happens.

cl3tUs · 01-22-2008, 12:39 PM

Okay, when I'm running sysprep.exe manually, I see the buttons for "Factory" and "Reseal".

Last time, I checked in the boxes for "Use Mini-Setup" and "Detect non-plug and play hardware". I kept the default setting for "Shutdown" and then clicked "Reseal". Is this the right way?

cl3tUs · 02-08-2008, 06:50 PM

I downloaded a new Sysprep and tried to Sysprep manually and it seemed to do better, but I wanted to run it manually.

I ran this manually using the sysprep.exe -bmsd. Once that was done, it plugged in the mass storage info. I put this sysprep.inf onto my external HD and kept it handy. I put it on my Sysprep_New folder for my testing on the server. After that finished, I ran a sysprep.exe -mini -reseal -forceshutdown and sysprep actually ran. Problem is that I captured that Sysprepped image and the pushed it to a different computer of the same model (HP D530 SFF) and it wouldn't pull down my NIC driver. On top of that, it dropped having a driver for ECP Printer Port.

After that, I tried to have Altiris Deployment Console sysprep for me and that didn't work. Sysprep ran in 30 secs.

We are also doing something where we edit the registry at HKEY_LOCAL_MACHINE and we drill down to the Software > Microsoft > Windows category where they have the "Device Path" entry and we change that to where we install the Drivers by default from the C:\Drivers. Usually, the NIC is the only thing that installs and we have scripts that install everything else. I didn't know if that would change anything or not, but we keep the entry the same, we just add more to that path.

Is there something that I'm doing wrong?

cl3tUs · 02-12-2008, 10:44 AM

I had to sysprep manually, but when I tried to capture that sysprepped image, my job wanted to "restart the computer to prepare for imaging", and I couldn't have it hit windows, so I had to send a pause script in WinPE and then use that other window to navigate to F:\Rdeploy\rdeploy.exe and then upload my sysprepped image.

I can send the image down, but the computer doesn't have the NIC driver when it comes up. I made changes to the Unattend due to advice from the IRC channel and the forums.altiris site. The changes are listed below:

[Unattended]
UnattendMode=FullUnattended
OemSkipEula=YES
OemPreinstall=YES
UpdateInstalledDrivers=NO
DriverSigningPolicy=IGNORE
OEMPNPDriversPath="c:\drivers\chipset;c:\drivers\v ideo;c:\drivers\audio;c:\drivers\nic_broadcom;c:\d rivers\nic_intel"
KeepPageFile=0
NoWaitAfterTextMode=1
NoWaitAfterGUIMode=1
ExtendOEMPartition=1
InstallFilesPath=C:\sysprep\i386
ResetSourcePath=c:

The drivers are in those locations. The main driver I'm concerned about is my NIC. I can't seem to get my computer to pull that driver. The computer also doesn't join to a domain, which can be from the NIC driver not being installed, but if we fix that and it doesn't domain join, I'll have to figure something else out.

khanlin · 02-20-2008, 01:08 PM

Try this sysprep.inf file. I have stripped all sensitive data, so you'll need to enter your password, key, ect... But this works for me on all platforms we have. The OEMPNPDrivers section is a place that you can FIRM drivers to the HD for MiniSetup to find drivers. Give it a try.

cl3tUs · 02-20-2008, 01:16 PM

Impressive. Do I need all that? What is the "Sysprep CLeanup"?

dstclair · 02-22-2008, 02:35 AM

I've run into the problem you're having a number of times. The solution is actually quite simple, although seemingly completely unrelated to everything else. Do the following (key parts):
sysprep -bmsd
sysprep -clean
Then actually run sysprep (doesn't matter exactly how you do this part):
sysprep -mini -reseal (or via the interface)

And that should take care of it for you.

Let me know how that turns out.

cl3tUs · 02-22-2008, 02:10 PM

I didn't do the sysprep -clean when I did it. It seems to be working except for joining it to the domain, but I've been doing some research on that and a lot of people are saying that sysprep is good, but tends to not work at times and that I can use something called netdom.exe to join it to the domain.

dstclair · 02-22-2008, 03:03 PM

If you have the aclient in the image a modify configuration job after the fact works well.

cl3tUs · 02-22-2008, 03:12 PM

We currently do that. Before, sysprep took care of everything and we never had too. Now, we do and it takes another minute or 2 to finish and then continue to the next job. Sure, 2 minutes isn't much, but people's faith in Altiris around here is not very high due their own computers and stuff they allow people to do.

I'm going to try to see what I can figure out.

dstclair · 02-22-2008, 06:03 PM

The number one reason that it doesn't join is that network drivers aren't available in my experience. Or the domain has settings preventing it from joining.

Also, when the domain join fails you generally have to hit ok to continue the sysprep unsealing process making it not a zero touch deployment. Where with the modify configuration task it will at that point either have network drivers, or if not, its moot. And it gives you a nice error in the DS console, but remains zero touch.

cl3tUs · 02-25-2008, 09:42 AM

At first, it didn't have the NIC driver, but now I do and it still doesn't join. Prob is that I'm not getting any error. I don't know whether to be happy or not. No errors = awesome...but on the other hand, it's not doing what I need it to.