Jump to content


d0zer

My first SCCM 2007 and Deployment

Recommended Posts

Hello Community,

 

 

i am new to this community. i´m from germany and my english is not the best but i hope that you understand what i mean ;)

i´m also still in education (last year from 3) and not so practised with the whole windows server thing.

 

 

and now to my concern.

 

 

i got the task from my boss, to set up a Server, which can deploy Software and Operating Systems. We use XP, Vista and Win 7. But the focus should be on Vista and Win 7.

 

 

What need i, to deploy Applications and OS ?

 

- Server 2008

- Windows Deployment Server on Server 2008

- SCCM on Server 2008

 

am i right? What do i also need, to deploy Applications and OS?

 

 

We have a separate DHCP Server which is configured and managed by a cisco server and software.

We also have 2 Domain Controllers.

I just want to know, if i can install the 3 points above separate or have the WDS and the SCCM to be installed on the DC´s and DHCP. This would be a Problem, because DHCP is Cisco.

 

 

 

 

For the installation i will reade the guides here and than post my problems :)

 

 

I hope that you can help me and thank you.

Share this post


Link to post
Share on other sites

welcome to the forums and to SCCM 2007

 

you'll need sp2 beta for sccm if you want to deploy windows 7 or windows server 2008 R2,

 

you can separate your installation servers into two separate servers, one doing AD, DNS and the other doing SCCM and SQL and WDS (and optionally MDT)

 

what operating system is your DHCP server running ?

 

good luck

Share this post


Link to post
Share on other sites

well i don't know ifit will work but we'll do our best to try and get it working, i know we managed to get sccm working with an nt4 DHCP server so I can't see why solaris won't work

Share this post


Link to post
Share on other sites

Hello again

 

i´m now setting up a Server 2008 with WDS and SCCM.

The prerequisite check shows me 4 points:

 

- "WSUS SDK on site server"

- "sql server sysadmin rights" (i´m working with my domain account and i added me to the sysadmin role but this point is still there)

- "domain membership" (the server is already in a domain, what´s the problem?)

- "short file name (8.3) support (site system)"

 

 

how to fix points 1-3 ?

 

 

thank you

Share this post


Link to post
Share on other sites

wsus is just a warning you can ignore it and install it later

 

can i see a screenshot of this server and are you logged onto the domain ?

 

is sql Server on a different box to sccm ? not recommended.....

Share this post


Link to post
Share on other sites

Here is a screenshot with all windows you need i think.

 

i´v hide my real account with "domain\myaccount"

 

you see, that my account (domain account) is in the role "sysadmin" and i am also logged in in the domain currently on the image.

 

 

 

PC1246 is the computer where server 2008 is installed and where i want to install SCCM.

 

 

 

 

 

The name "SCCM2007", how i called it, is just the name for the sql server or has it to the be same as PC1246 ?

 

 

SQL 2005,WDS and SCCM are planned to run both on the PC1246. Are there problems, when all 3 run on one machine ?

 

 

Which Server is the site server ? i don´t understand this, because there is no german documentation. Is the site server the Domain controller

?

post-3605-12518172045011_thumb.jpg

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.