Eswar Koneti

Nothing wrong from the log files. All seems to be fine.Can you intiate the machine policy retrival and see what happens ? From the advanced tab,click on Site code discover .

Did you see ccmsetup.log ? if the client installation is succeded or not? also see if you are able to disover the sitecode .Are you sure the boundaries are added correctly for these machines ? with a single line from the log files is hard to anylase what could be the problem. can you zip and post locationservices.log,clientlocation.log and ClientIDmanager.log here ?

It is hard to say with these failed sentances direclly.There should be other information after and before task action failed. It would be easier for us if you post smsts.log for other info as well. this could be because of command line syntax errors for do X86 scanstate or not having the required USMT package? it is failed to connect to ABC00005(might be boot image),also problem could be network breakdown issues or secury rights(may be NAAccount ) while connecting to PXE DP package but after this messgege ,client should have tried connecting again to this package successfully i think.

the other policy agents only comes if the client is able to talk to Management point and is assigned to correct site. check the client log files (locationservices.log,clientlocation.log,ccmsetup.log) to find whats wrong ? check issues like WMI or firewall etc ?

All the clients shoud report on their next DDR cycle with updated information. Why dont you Use SCCM Collection commander http://sourceforge.n...cts/smscollctr/ to generate New GUID for all the computers in one shot ? OR apply Group policy to generate New GUID for the computers ?

Ah..Its my Bad.....Reprorting point services is installed fine but reporting point installation information is loged into srsrp.log(i was not looked at this log before) and site is added trusted sites to make it work and there is no applications created in IIS for this role. You can also see SMS_SRSRP folder, will be created under Vnext installation drive(E:\SMS_SRSRP\Reports\) with catagory wise(asset intellegnce,hardware,software distribution etc) folders.

In addition to above,check the credentials which you provided to join the computer to domain if it has rights ?

SCCM will inventory all the values based on sms_def.mof .If you need additional values to be extended, you can check this by sms_def.mof file from your SCCM installation drive:\inboxes\clifiles.src\hinv\sms_def.mof ?

are you talking about window which prompt to accept the license aggrement when deploying win7 if am not wrong ? If so, win 7 OS which is not ultimate Edition like enterprise or someother,you will not see any prompt to ask for License aggrement until you provide the correct product key in Task sequene since Enterprise etc edition will not have Product Key(they are activated Via KMS OR MAK)

You will have to create collection under quiries section to prompt for hostname,btw,where are you creating this ? Try creating this collection/report: http://wmug.co.uk/bl...n-computer.aspx and here is summary of computer information http://eskonr.wordpr...cm-web-reports/ Moving this post under collection section.

What does smsts.log says ?

If you are not using SCCM R2 version,then you should import the Target MAC ID or UUID into SCCM Database,in this process it asks you to make this computer part of which collection and then advertise the Task sequence to the collection .Hope you should have done the same process. If the computer doesnt have any Task sequnces advertised to it,it will not Boot into WinPE until it recives any. Check if the MAC which you have imported correctly or not and it is part of Targeted collection.

May be there is no specific log file present on the client log folder .Can you please check if the log which you are looking at is really there or not with info \\clientname\windows\system32\ccm\logs

Check if the packages which are used in Task sequence are availble in DP or not with correct Package version also ensure the NAAccount is correctly configured ?

Recomendeded is ,set the Password Never Expires for Network access account

Nope,i did not missed any thing but rather to use Credentials stored securely in the report server ,i use windows security (that doesnt make any issues i guess) and rest of the things went well but when i am at New Site Role wizard appears,i can see both my SCCM and Vnext as well.so i select Vnext which host RSP role. But wonder why smsreporting log is not created. On different server(where Vnext is installed) which has its own SQL server Database,it works without any issues and i can able to generate new reports as well.

Running SCCM 2007 and Vnext on same SQL Box(which is running on SCCM server).windows runnnig on Server 2008 X64. Trying to install Reporting services point role in Vnext server,role is installed (from the GUI showing all green tick marks) but no logs are created in Vnext server to see what went . And No information in IIS about reporting role. No reports are displayed under reports node in SCCM server ,not even http://in-vnext/reports working. any thoughts?

From the log information,it tells that,you have not distributed the packages to DP which you used in the Task seqeunce. Look at thsi post here

First ,there are different SCCM client installation methods are present and decide which method to use ,based on this,you can troubleshoot accordinly. If you go with client push installation method,you would require client installation account ,for monitoring the status,you can look at ccm.log. If you have installed the client by any other method and the client is installed sucessfully(from ccmsetup.log) but failed to get site code or someother issue,you can post it here for further troubleshooting. There can be a lot of reasons for client failure and requires troubleshooting.

This could be because of PAckage (MS10004)which is not avilable in DP ? Are you using Any drivers action(auto apply drivers ) ? or any product key in Task sequence ? or problem with your sccm client package ?

Patches which do not have MS Bulletin ID numbers are Hotfixes which are applied to fix Bug on computers. These hotfixes doesnt have any clasification or severiaty rating like Security/critical rating as MS Bulletin ID's have.

Nope,the default boot program (optional) is only avilable in Server 2008 (not R2) and server 2003(if you want to reaplce boot files).But this is replaced with options that i posted another blog since server 2008 R2 gives you a GUI to select or not pxeboot.com.

When you update the package source files ,,you need to distribute it to DP.This will update the package with a new version and the client will download and install.Also check if you have any hidden files in the pakage Try updating the DP and see if that works out. Here is some info refresh and update DP fromt technet

attachement is missed ;-)

did you see ccm.log on the site server to see if the give client push instllation account has any issues or not ?